1257908 - crash in shutdownhang | ntdll.dll@0xa5154 | Modal dialog causes shutdown hang

Status: RESOLVED DUPLICATE of bug 1274399

(Core :: DOM: Core & HTML, defect)

Description

[Benoit Girard (:BenWa)]

This bug was filed from the Socorro interface and is 
report bp-2b558ab9-cc0e-4909-b718-d0a472160312.
=============================================================

Looks like some of this signature is caused by having a modal dialog blocking shutdown.

Comment 1

[Andrew Overholt [:overholt]]

BenWa, do you know of a simple STR here?

Comment 2

[Benoit Girard (:BenWa)]

no, this isn't my crash. But we could try to create a dialog and queue a shutdown request. Perhaps even one of those 'Are you sure you want to leave this page with unsaved data' prompt?

Comment 3

[Andrew Overholt [:overholt]]

(In reply to Benoit Girard (:BenWa) from comment #2)
> no, this isn't my crash. But we could try to create a dialog and queue a
> shutdown request. Perhaps even one of those 'Are you sure you want to leave
> this page with unsaved data' prompt?

Interesting idea. I don't know who to ask about their thoughts on this ... Boris?

Comment 4

[Boris Zbarsky [:bzbarsky]]

I wish we had JS stacks in breakpad...

In this case, looking at the stack for thread 0, it looks like we start in nsUpdateProcessor::UpdateDone and that calls um->RefreshUpdateStatus().  That runs a bunch of JS (because nsIUpdateManager is implemented in JS), and eventually does something with a double-wrapped (in XPCWrappedJS and then XPCWrappedNative) JS object, which runs more JS, which does another call on a double-wrapped, which runs more JS, which explicitly calls nsWindowWatcher::OpenWindow via XPConnect.  Presumably opening a modal window.  Could be extension code at this point...

It's possible we've queued up a shutdown by this point already from the update manager stuff; I haven't looked into that code.