If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Firefox hangs after the main window disappeared




8 years ago
8 years ago


(Reporter: Marcos García, Unassigned)



3.5 Branch
Mac OS X

Firefox Tracking Flags

(Not tracked)


(Whiteboard: stackwanted)



8 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; es-ES; rv:1.9.1) Gecko/20090624 Firefox/3.0.5 MEGAUPLOAD 1.0
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; es-ES; rv:1.9.1) Gecko/20090624 Firefox/3.0.5

Suddenly, the main window disappeared, and Mac OSX said the app didn't respond, so I did CMD + Q, and then i got "Firefox crashed" (the usual Mac OSX window) then i could load firefox as usual.

Reproducible: Sometimes

Actual Results:  
Firefox crashed

Expected Results:  
It should act as usual

Report here: http://firefox.pastebin.com/f76e9034

Comment 1

8 years ago
Could you please provide the crash id?

Severity: major → critical
Keywords: crash
Whiteboard: crashidneeded
Version: unspecified → 3.5 Branch

Comment 2

8 years ago
Because the Firefox Crash Reporter window didn't appear, i dont have any crash ID

Comment 3

8 years ago
This problem also happened to me a few times in the 3.0 branch

Comment 4

8 years ago
so. the dialog you got let you force quit. it wasn't showing you a crash, it was showing you a hang.

from your log:
Event:          hang

your stack was somewhere under js, beyond that i can't see anything interesting.
Summary: Firefox crashes after disappearing the main window → Firefox hangs after the main window disappeared
Whiteboard: crashidneeded → stackwanted

Comment 5

8 years ago
So... isn't this a bug?
(In reply to comment #5)
> So... isn't this a bug?
perhaps, but much information is needed before it can be confirmed as a bug.

please read the page linked in comment #1

Comment 7

8 years ago
If you want to get a stack trace for a hang, you need to download a dmg with -shark- in its name. Then you can use activity monitor/sampler.app to get a stack trace.

since you don't have a stack usable trace, this bug is incomplete.
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.