No, what happens is that Flashblock won't block the Flash elements from loading (they load the instant I scroll the page using the sidebar, even though I'm careful not to click on the Flash stuff itself). When the Flash elements load, that seems to be what causes the CPU load spike in browserd that shuts the browser down.

I never had a problem with the Flash stuff before a couple of days ago (about when I loaded the 30-2 update). And I've only had the problem on the NY Times website. I sent them an email to see if they have any explanation. I guess I'll try reflashing again and this time not accepting the 30-2 update and see if that does anything.