Closed
Bug 615034
Opened 15 years ago
Closed 14 years ago
"ASSERTION: Element without owner document" with GC'd document
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jruderman, Unassigned)
References
Details
(Keywords: assertion, testcase)
Attachments
(2 files)
1. Install 'DOM Fuzz Lite' from
https://www.squarefree.com/extensions/domFuzzLite.xpi
2. Load the testcase.
###!!! ASSERTION: Element without owner document: 'Error', file content/base/src/nsGenericElement.cpp, line 3419
Reporter | ||
Comment 1•15 years ago
|
||
![]() |
||
Comment 2•15 years ago
|
||
Yeah, this assert is semi-bogus while documents can go away before their elements.
Luckily, we're planning to fix that...
Comment 3•15 years ago
|
||
Although I'm not sure whether we will actually force documents to live longer
than elements during unlink.
![]() |
||
Comment 4•15 years ago
|
||
Sure, but that shouldn't be an issue for this testcase.
![]() |
||
Updated•14 years ago
|
Depends on: strongparent
Comment 5•14 years ago
|
||
Jesse, this is fixed, right?
Reporter | ||
Comment 6•14 years ago
|
||
Yes.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 7•13 years ago
|
||
So should elements always have an ownerDocument then, ideally? Because I'm seeing currently a js error in one of my GreaseMonkey scripts that says that some element.ownerDocument is undefined.
Comment 8•13 years ago
|
||
element.ownerDocument should always point to a valid document.
.ownerDocument is defined in nsIDOMNode, so if ownerDocument is undefined, it sounds like
element isn't actually element object but something else.
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•