Luke, any idea who might be able to debug this?
That error appears to be reported by the DeadObjectProxy which gets created when we sever chrome's connection to a content window when it's time for that content window to die. khuey added this way back; he might have better tips for debugging these, but, if nothing else, I'd put a breakpoint on ReportDead (in a DEBUG build): http://mxr.mozilla.org/mozilla-central/source/js/src/proxy/DeadObjectProxy.cpp#18 and, when that hits during shutdown, call js::DumpBacktrace(cx) (from the debugger) http://mxr.mozilla.org/mozilla-central/source/js/src/jsobj.cpp#3617 to print out the JS callstack.
What Luke said, pretty much.
Jonathan, can you still reproduce this?
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.