9 years ago
9 years ago


(Reporter: fredcone, Unassigned)


({crash, stackwanted})

3.0 Branch
Windows Vista
crash, stackwanted

Firefox Tracking Flags

(Not tracked)





9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv: Gecko/2009040821 Firefox/3.0.9 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv: Gecko/2009040821 Firefox/3.0.9 (.NET CLR 3.5.30729)

Crash While Idle

With the following set of 6 tabs open, it seems fine until the monitor (not the PC) goes to sleep (power save mode).

When I move the mouse to wake it up, I see the message that Firefox was shut down due to an error.

The first time it happened, I did not know what I had open when it crashed, so I filled out the "Breakpad" Mozilla Crash Reporter dialog that popped up with the comment "Sitting idle".
The next (3, so far) times it crashed, the Mozilla Crash Reporter dialog did not pop up, instead I got the following dialog box:

| Microsoft Visual C++ Runtime Library
| Runtime Error!
| Program: C:\Prpgram Files (x86)\Mozilla Firefox\firefox.exe
| This application has requested the Runtime to terminate it in an unusual way.
| Please contact the application's support team for more information.

Firefox 3.0.9
Windows Vista Home Premium 64-bit
HP Pavilion a6650f with an AMD Phenom X4 64-bit processor

Reproducible: Always

Steps to Reproduce:
1. Open these 6 URLs in tabs
2. Allow monitor to go to sleep (power save mode) (not necessary to wait for PC to sleep). This takes about 30 minutes on my system.
3. When mouse is moved, Firefox has crashed.
Actual Results:  
Message that Firefox has crashed as described above in Details above.

Expected Results:  
Tabs should still be open in Firefox.


Build platform

Build tools
Compiler 	Version 	Compiler flags
cl 	14.00.50727.762 	-GL -wd4624 -wd4952 -TC -nologo -W3 -Gy -Fd$(PDBFILE)
cl 	14.00.50727.762 	-GR- -GL -wd4624 -wd4952 -TP -nologo -Zc:wchar_t- -W3 -Gy -Fd$(PDBFILE)

Configure arguments
--enable-application=browser --enable-update-channel=release --enable-optimize --disable-debug --disable-tests --enable-update-packaging --enable-official-branding --enable-jemalloc --with-crashreporter-enable-percent=10
Do you have the VLC plugin installed (look in about:plugins) ?
and please read


9 years ago
Severity: normal → critical
Keywords: crash
Version: unspecified → 3.0 Branch

Comment 2

9 years ago
note that for the case where you get that dialog, you will need to follow the instructions from:

one of
!analyze -v -f
!analyze -v -hang

will provide the stack we need to determine the cause.

Comment 3

9 years ago
I do not know what the VLC plugin is, but about:plugins does not show it.

I did not understand the "How to get a stacktrace for a bug report" instructions.
I did not understand what a binary build from is. 

I opened

I installed the Debugging Tools for Windows 64-bit Version as described in "How to get a stacktrace with WinDbg", but the section "A Firefox nightly or release" was not adequate for me to understand what was required, therefore I could not "open the firefox.exe executable you downloaded before via File->Open Executable..." as requested in the section "Debugging".
When I opened either "official nightly build" or "" I got a list of files with no hint of which to choose, or what to do to download one.
A binary build is one that you download from When you open that link, download the right one for windows, which is a zip or exe. Using the firefox you have installed, type about:crashes in the addressbar, and copy a report id that corresponds to the crash time.

Comment 5

9 years ago
tyler: sadly if he's getting runtime dialogs, there will not be a crash report.

fred: as you aren't crashing at startup, you can run firefox first (normally), run windbg, and then instead of using file>open executable, you can use file>attach to a process. you're looking for firefox.exe in that list. typically it will be near the end, if you need to you can sort by executable which would place it closer to the beginning, select it and then click ok.

that'll get you to the process, and then you can follow the rest of the steps (.sympath, .symfix, .reload, !analyze)
Keywords: stackwanted
Summary: Crash While Idle → c++ runtime abort
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.