Two Sites that cause fatal Fx problems

[therube]

(Haven't really followed, but...)

Existing Profile
A number of extensions; ABP, cZ, Console2, FlashGot, NoScript, Shumway...
Restore from Session Restore
- Noscript, Allow Scripts Globally
Open your four links

RAM:
- SeaMonkey 402 MB
- plugin-container 402 MB (one of these is wrong, they weren't the same, but close)
CPU (dual core):
- SeaMonkey, variable ~7%
- plugin-container, variable ~36%

There is a lot of active content on those pages.
Anyhow, a lot of crap going on, simultaneously, including a lot of disk paging (as I have much else open too). Individually, SeaMonkey isn't using much RAM. Together (with plugin-container, aka Flash if you will) its using a decent amount.

Anyhow, all is up, loaded, & running (at least reasonably well).

XP SP3
Intel E4300, 1.8GHz
2GB RAM
9GB free disk space


> temporarily transfer me to Thunderbird and then back to Fx

That sounds like Flash.
Typical that the first time Flash fires, you're transferred, elsewhere.

[Fatal Sites]

"Aye, there's the rube."

I have never been transferred to some other location when viewing a Flash video on a page that is specifically for a video, but perhaps that I am transferred elsewhere when trying to read news feeds that contain flash items works differently. When I do get transferred, it does not happen just once, it usually happens several times, and sometimes it never stops happening until I kill Firefox.

I've also discovered another oddity, namely that if I do not block NBC News in YesScript, I don't see anything on the monitor. I don't see many NBC News RSS feeds, only a few that other feeds pick up, so it took me a few days to realize that I even have a problem seeing the items. I loaded one or two before blocking the site, and then pressed Ctrl-U, which clearly indicated that the pages were loaded, as well as showing a truly overly-complex set of script codes. Why blocking the site allows them to then appear on the monitor is just another aspect of this entire problem.

The problems I've encountered with ABC News, ATWonline, and Politico are all recent ones, problems that i never had say two months ago. I still have no idea if they are caused by the sites have poorly implemented code changes, or if something has changed in a recent Fx''s javascript decoder, nor do I have any way of figuring out which, or both, of these possibilities is correct.