515361 - broswer_privacypane_* tests cause lots of XPConnect assertions

Status: NEW

(Firefox :: Settings UI, defect)

Description

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

The browser_privacypane_* tests cause a large number (somewhere around a hundred; much less than bug 510489) of assertions about calling XPConnect on a scope without a Components property.  In other words, they're trying (and failing, most likely) to execute JavaScript in the context of a window that's already been closed.

I'll attach the C++ and JS stack of one such assertion, from the debugging output in bug 510489.

Comment 1

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

Attachment: output

A relevant chunk of the output from the other bug, containing multiple stacks.

Comment 2

[(no longer active)]

I specifically wait in that test for each window to be closed and send the domwindowclosed notification before proceeding to run the next test.  What other scenarios are conceivable for such an assertion?

BTW, how can I get a js stack at the assertion points locally?

Comment 3

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

(In reply to comment #2)
> BTW, how can I get a js stack at the assertion points locally?

Call js_DumpStackFrame, like in http://hg.mozilla.org/users/dbaron_mozilla.com/patches/raw-file/56363c473a65/no-components-dump-stack