Closed Bug 830448 Opened 12 years ago Closed 12 years ago

Hang while spinning the event loop during shutdown

Categories

(Firefox Health Report Graveyard :: Client: Desktop, defect)

Product:
Firefox Health Report Graveyard
Component:
Client: Desktop
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 828149

People

(Reporter: ehsan.akhgari, Assigned: gps)

Details

So here it seems like the JS event loop is waiting for an event which is never dispatched. This prevents Firefox from shutting down. https://gist.github.com/4532800
This is very bad.
tracking-firefox20: --- → ?
That log does not indicate that FHR has received a shutdown request. Since FHR is not receiving a shutdown request, FHR never spins the event loop. The FHR shutdown sequence is initiated when the "quit-application" notification is sent. Do you see anything in your logs indicating that "quit-application" or any part of the regular shutdown notification sequence is occurring?
Flags: needinfo?(ehsan)
Well, this is on the stack: http://mxr.mozilla.org/mozilla-central/source/toolkit/xre/nsXREDirProvider.cpp#864 So we send profile-before-change and then there's a JS handler which ends up calling nsThread::ProcessNextEvent at some point. Is that not an indication of the FHR event spinning code?
Flags: needinfo?(ehsan)
Tracking for 20 and looking for an assignee to work on this so throwing to gps.
Assignee: nobody → gps
tracking-firefox20: ? → +
I suspect this will be a dupe of bug 828149.
I'm very confident this is a dupe of bug bug 828149. Reopen if you can reproduce on m-c.
Status: NEW → RESOLVED
Closed: 12 years ago
status-firefox19: unaffected → ---
status-firefox20: affected → ---
status-firefox21: affected → ---
tracking-firefox20: + → ---
tracking-firefox21: + → ---
Resolution: --- → DUPLICATE
Component: Metrics and Firefox Health Report → Client: Desktop
Product: Mozilla Services → Firefox Health Report
Product: Firefox Health Report → Firefox Health Report Graveyard
You need to log in before you can comment on or make changes to this bug.