Closed
Bug 621618
Opened 14 years ago
Closed 11 years ago
"ASSERTION: Removing id entry that doesn't exist" with <svg:use>
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
FIXED
mozilla30
Tracking | Status | |
---|---|---|
blocking2.0 | --- | .x+ |
People
(Reporter: jruderman, Assigned: dbaron)
References
Details
(Keywords: assertion, regression, testcase, Whiteboard: [mentor=bz][lang=c++])
Attachments
(6 files)
135 bytes,
text/html
|
Details | |
5.73 KB,
text/plain
|
Details | |
2.78 KB,
patch
|
bzbarsky
:
review+
|
Details | Diff | Splinter Review |
4.27 KB,
patch
|
bzbarsky
:
review+
|
Details | Diff | Splinter Review |
1.89 KB,
patch
|
bzbarsky
:
review+
|
Details | Diff | Splinter Review |
2.66 KB,
patch
|
bzbarsky
:
review+
|
Details | Diff | Splinter Review |
1. Load the testcase.
2. Close the tab or window or quit Firefox.
###!!! ASSERTION: Removing id entry that doesn't exist: '!aElement->GetOwnerDoc() || !aElement->GetOwnerDoc()->IsHTML() || mIdContentList.IndexOf(aElement) >= 0', file content/base/src/nsDocument.cpp, line 425
(Same assertion as in bug 593302, which had a very different testcase.)
Reporter | ||
Comment 1•14 years ago
|
||
Could be bad, but I need to investigate. Definitely a regression since id handling is much more sensitive now.
Comment 3•14 years ago
|
||
I think we can ship 2.0 w/o this, but if this is more severe than we think we'll reconsider.
blocking2.0: ? → .x
Reporter | ||
Comment 4•13 years ago
|
||
This can lead to additional badness, such as
ASSERTION: No Document Request!: 'mDocumentRequest', file uriloader/base/nsDocLoader.cpp
ASSERTION: Firing OnStateChange(...) notification with a NULL request!: 'aRequest', file uriloader/base/nsDocLoader.cpp
Comment 6•12 years ago
|
||
This is being hit by dom/plugins/test/mochitest/test_bug813906.html
Comment 7•12 years ago
|
||
The basic issue here is that things only add themselves to the id table if they're not anonymous, but they remove unconditionally....
Whiteboard: [mentor=bz][lang=c++]
The patch in bug 741295 would fix this I'm pretty sure.
Depends on: 741295
Hmm.... on second thought, maybe it wouldn't.
No longer depends on: 741295
Assignee | ||
Comment 10•11 years ago
|
||
This is the most common assertion I see, since it shows up all the time on the http://www.openstreetmap.org/ iD editor.
Assignee: jonas → dbaron
Assignee | ||
Comment 11•11 years ago
|
||
Assignee | ||
Comment 12•11 years ago
|
||
I think this could have been done as part of Bug 700981 part 2, which
moved AddToIdTable and RemoveFromIdTable calls from nsStyledElement to
nsGenericElement.
Attachment #8384428 -
Flags: review?(bzbarsky)
Assignee | ||
Comment 13•11 years ago
|
||
Attachment #8384429 -
Flags: review?(bzbarsky)
Assignee | ||
Comment 14•11 years ago
|
||
Attachment #8384430 -
Flags: review?(bzbarsky)
Assignee | ||
Comment 15•11 years ago
|
||
Attachment #8384431 -
Flags: review?(bzbarsky)
The patch in bug 741295 probably also fixes this one.
Assignee | ||
Comment 17•11 years ago
|
||
Well, it certainly makes patches 1 and 2 irrelevant.
I'm not sure about patch 4, which is actually the part most relevant to the cases for which we have testcases for the assertion firing. It seems to make that inconsistency worse.
Comment 18•11 years ago
|
||
Comment on attachment 8384428 [details] [diff] [review]
patch 1: Remove BindToTree overrides in nsXMLElement that exist only to make AddToIdTable/RemoveFromIdTable calls already in the base class (Element)
r=me
Attachment #8384428 -
Flags: review?(bzbarsky) → review+
Comment 19•11 years ago
|
||
Comment on attachment 8384429 [details] [diff] [review]
patch 2: Make nsXMLElement reuse Element::AddToIdTable and Element::RemoveFromIdTable thoroughly
r=me
Attachment #8384429 -
Flags: review?(bzbarsky) → review+
Comment 20•11 years ago
|
||
Comment on attachment 8384430 [details] [diff] [review]
patch 3: Add FIXMEs in nsXULDocument for ID handling
r=me
Attachment #8384430 -
Flags: review?(bzbarsky) → review+
Comment 21•11 years ago
|
||
Comment on attachment 8384431 [details] [diff] [review]
patch 4: Make conditions in Element::RemoveFromIdTable match those in AddToIdTable, to avoid asymmetric calls to the document's functions
r=me
Attachment #8384431 -
Flags: review?(bzbarsky) → review+
Assignee | ||
Comment 22•11 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/57d5722c785b
https://hg.mozilla.org/integration/mozilla-inbound/rev/5bd1a27cf9e6
https://hg.mozilla.org/integration/mozilla-inbound/rev/90990d488dcc
https://hg.mozilla.org/integration/mozilla-inbound/rev/50462316925c
(see also try run at https://tbpl.mozilla.org/?tree=Try&rev=d7e48cf00e0e)
Flags: in-testsuite+
Comment 23•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/57d5722c785b
https://hg.mozilla.org/mozilla-central/rev/5bd1a27cf9e6
https://hg.mozilla.org/mozilla-central/rev/90990d488dcc
https://hg.mozilla.org/mozilla-central/rev/50462316925c
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla30
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
•