Closed
Bug 1265661
Opened 8 years ago
Closed 8 years ago
JavaScript error: , line 0: TypeError: can't access dead object
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jwatt, Unassigned)
Details
During shutdown of debug builds I get a lot of these lines: JavaScript error: , line 0: TypeError: can't access dead object
Reporter | ||
Comment 1•8 years ago
|
||
Luke, any idea who might be able to debug this?
Flags: needinfo?(luke)
Comment 2•8 years ago
|
||
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.
Flags: needinfo?(luke)
What Luke said, pretty much.
Reporter | ||
Comment 5•8 years ago
|
||
No.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(jwatt)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•