• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Serious problem with latest Firefox 3.5.3

Deanodarlo

Senior member
I've found with this Firefox, if you block cookies at a download site like CNET and have Javascript enabled (ie don't have noscript) then...

...when you try and download a file you'll get 100% CPU load and a Firefox process running away with a memory leak (100's of MB's of RAM in a few seconds).

For example, if I download this file without allowing cookies, then Firefox will go crazy:

http://www.cnet.com/firefox-3/

I've re-installed Firefox, started with a fresh profile and found when I block cookies (using Cookie Monster, Cookie safe or simply disabling cookies in the options) then this problem occurs.

Anyone else who blocks cookies noticed this?
 
No, but I've quite trying to use the latest FF because no updates and no re-installs would make it work well. I was having to hit the reload key every 4-5 sites because it would say it couldn't find the site at first, then it would when I hit reload. I don't know when FF will work well again. Maybe 3.6?
 
No one else have this major issue?

It's repeatable on three different machines I've tried, even on a fresh install of Firefox with no extensions. You'll get 100% CPU usage (50% or 25% on multi-cores) and a run away memory leak until you kill firefox via task manager.

All you have to to is block cookies and have Javascript enabled, then certain websites will always crash the browser.

I'm disappointed that firefox still has such random CPU and mem bugs after all this time. Can't give it up though - I like the extensions too much.

As you said DBisset, role on 3.6!
 
Well, I've started a thread on the main Firefox forum, where loads of people are reporting similar issues, and see what they say. 🙂
 
Back
Top