All Firefox versions crash Windows Vista on certain websites




12 years ago
11 years ago


(Reporter: Jeff Supodsson, Unassigned)


2.0 Branch
Windows Vista

Firefox Tracking Flags

(Not tracked)


(Whiteboard: CLOSEME - 06/18, URL)



12 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.0.04506)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv: Gecko/20061204 Firefox/

When visiting certain websites, Windows Vista hangs entirely. This occurs on Firefox versions, 2.0,, and possibly others. These websites include: Bugzilla (here), Gmail, and Google's personalized homepage. I suppose that it happens with websites that have ajax or javascript, although I am unsure.

Reproducible: Always

Steps to Reproduce:
1. Open up Mozilla Firefox.
2. Browse to
3. Login if neccessary.
4. Return to previous page.
Actual Results:  
Mozilla Firefox continues to load page until the ajax boxes appear, then freezes. Windows Vista also freezes. Keyboard and mouse become unresponsive.

Expected Results:  
Mozilla Firefox should have loaded the ajax boxes and the entire homepage.

Mozilla Firefox: default settings
Hardware: AMD Athlon XP 2800+, 1GB RAM, 80GB HDD, Windows Vista Ultimate Edition
Did you also test this with a new profile without extensions and themes?

Comment 2

12 years ago
It was a new install, and the first thing I do is change my homepage. Since is my regular homepage, that was the first thing I did.
WFM with Firefox 2 / 1509/ 2001. 

Do you have a Talkback ID from theses crashes ?

Comment 4

12 years ago
How can I even submit a crash report? The whole OS crashes, unable to perform the task to save the report and submit it.

Comment 5

12 years ago
if you actually get a bsod, please follow steps from bug 321723 comment 8

Comment 6

12 years ago
Okay, I just tried the debugging application. I attached it to my Firefox process and browsed to said The system continues to lock up entirely. There is no BSOD or memory dump created. No dump is able to be created by the debugging program either.

Comment 7

12 years ago
if the system isn't actually crashing, and the browser isn't actually crashing then you'll need to read about how to configure windbg for live kernel debugging (note: i've never done this and i don't intend to play w/ it). you can read about livekd in the windbg help.

probably the simplest thing to do is to run taskmanager, go to the processes tab, right click firefox and change its priority to below normal.

don't close task manager. and lastly, try loading the fatal url.

task manager will run w/ a high priority and should leave a cpu usage indicator in your system notification area.

assuming firefox is just pegging your cpu, the light should change from dark green to bright green, but the system (especially task manager) should remain responsive.

Comment 8

12 years ago
Okay, I tried the task manager thing. The Firefox process at the time of the system lockup, I did notice somewhat high CPU usage. The CPU level went up to 64 and the memory stopped at 16,548 kb.

I'm going to try the live debug now.

Comment 9

12 years ago
Unfortunately, I am unable to do kernel (live) debugging because I do not have a secondary computer at hand. I tried clicking on local kernel debug, but the workspace window opens and closes before I can read what it's saying.

Trying Firefox again at normal priority, I got another result: CPU 17 / Mem 16xxx k

Unfortunately, IE7 also crashes (ajax not involved, just multiple windows), but does not hang the system. This is a final copy of Windows Vista, but I would like to konw if there are also many others with the same problem.

Comment 10

11 years ago
I have the same problem.
Firefox and Windows Vista Ultimate 64bit crashes.
I tried builds from 2007-02-13 on.
Jeff Supodsson, can you try if you also crash/hang with the latest release Firefox ?
OS: Other → Windows Vista
Version: unspecified → 2.0 Branch
Jeff, Heinz, do you still see this crash in the latest Firefox Release ?

If so, could you provide a Talkback ID from the crash ?
Whiteboard: CLOSEME - 06/18
Closing as INCOMPLETE due to lack of information. Please address comment 12 before reopening.
Last Resolved: 11 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.