Firefox overheats laptop and eventually crashes.




8 years ago
8 years ago


(Reporter: lil_cool_dude, Unassigned)



Firefox Tracking Flags

(Not tracked)


(Whiteboard: [CLOSEME 2011-2-25], URL)



8 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:2.0b1) Gecko/20100630 Firefox/4.0b1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:2.0b1) Gecko/20100630 Firefox/4.0b1

Firefox appears to overheat (the laptop it's running on), slow down, and eventually crash when one or more webpages with non-valid code are open. it would appear that the processing and storage of error filled code is badly handled by firefox, as the longer a bad page is open, more and more RAM and CPU is used by the firefox, eventually causing the program to slow down to a crawl, and if left long enough crash the program entirely.

Reproducible: Always

Steps to Reproduce:
1. Open page with invalid code
2. Wait
3. Try to open a new tab
Actual Results:  
firefox is running so slowly that open the new tab takes a very long time, and over all responsiveness of the computer is diminished

Expected Results:  
the tab should open as it would if the error page had not been left open (open quickly and lag free)

i do not recall the bug occurring before firefox 3.6.3 but even downgrading now seems to give the same results on most versions. the laptop's that i can reproduce the bug on have ample resources and can open the same pages in other browsers, such as google chrome, without such a bug occurring at all. i have also tested using Windows 7 Vista and Ubuntu all of which give the same results.
Please upgrade to 4.0b2 and try if it still happens with 4.0b2
Please go to about:crashes and copy the id number(s) from the relevant crash(es). Past that number into the comment so we can get a stacktrace. may help if you have problems.
Also ensure you update to the latest version of Firefox before retesting.
Whiteboard: [CLOSEME 2011-2-25]
Version: unspecified → Trunk
This bug has had the CLOSEME tag for several weeks and the date in the tag is far gone. If the reporter can still see this issue, Please retest with Firefox 3.6.x or later and a new profile ( Then please remove the closeme tag in the whiteboard, mark the bug against the proper version and comment on the bug.
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.