Closed
Bug 499006
Opened 15 years ago
Closed 14 years ago
Null pointer crash [@ nsINode::GetNodeParent] in [@ nsContentUtils::ComparePoints] using detach()'ed DOM range
Categories
(Core :: DOM: Selection, defect)
Core
DOM: Selection
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: MatsPalmgren_bugz, Unassigned)
References
Details
(Keywords: crash, regression, testcase, Whiteboard: [sg:closeme])
Crash Data
Attachments
(4 files)
Loading the attached testcase crashes Firefox trunk. It doesn't crash 1.9.1 or 1.9.0 builds for me. (all on Linux x86-64)
Reporter | ||
Comment 1•15 years ago
|
||
The range was GC'ed ?
Reporter | ||
Updated•15 years ago
|
Group: core-security
Comment 2•15 years ago
|
||
This seems like the same issue, except it seems to have a different regression range and different stacktrace, namely not.
Comment 4•14 years ago
|
||
Neither testcase crashes Firefox 3.6, Firefox 3.5.7, or a trunk debug build for me (on Linux). dveditz, any reason to keep this one open still?
Whiteboard: [sg:closeme]
Reporter | ||
Comment 5•14 years ago
|
||
It appears to have been fixed in the range 2009-10-05-03 -- 2009-10-06-03: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=1470fa9c9f01&tochange=8f1ba5c38bb1 Bug 520070 is in that range and the attached crash stack looks similar to the one in that bug. We should land the crashtests in this bug when bug 520070 is made public.
Status: NEW → RESOLVED
Closed: 14 years ago
Depends on: 520070
Flags: in-testsuite?
Keywords: regressionwindow-wanted
Resolution: --- → WORKSFORME
Reporter | ||
Comment 6•14 years ago
|
||
Reporter | ||
Comment 7•14 years ago
|
||
Landed crashtests: http://hg.mozilla.org/mozilla-central/rev/09336169ed68 I think we can make this bug public now.
Reporter | ||
Updated•14 years ago
|
Flags: in-testsuite? → in-testsuite+
Assignee | ||
Updated•13 years ago
|
Crash Signature: [@ nsINode::GetNodeParent]
[@ nsContentUtils::ComparePoints]
Updated•9 years ago
|
Group: core-security → core-security-release
Updated•9 years ago
|
Group: core-security-release
You need to log in
before you can comment on or make changes to this bug.
Description
•