Closed Bug 307444 Opened 19 years ago Closed 19 years ago

SVG crash [@ nsContentIterator::NextNode]

Categories

(Core :: SVG, defect)

PowerPC
macOS
defect
Not set
critical

Tracking

()

RESOLVED FIXED

People

(Reporter: jruderman, Assigned: bzbarsky)

References

Details

(Keywords: crash, fixed1.8, Whiteboard: [sg:critical?]fixed by bug 278472)

Crash Data

Attachments

(1 file)

Attached file testcase (not reduced)
Blocks: stirdom
At the very least, the problem described in bug 278472 comment 5 is biting us here. Do we need to get this fixed for 1.8? If so, I better start working on bug 278472 soon...
Depends on: 278472
> Do we need to get this fixed for 1.8? Yes, because: * This crash occurs frequently on every page in the W3C SVG test suite when I use the "Stir DOM" bookmarklet, so this crash prevents me from testing all of those pages for other crash and hang bugs. * I'd like to make the "Stir DOM" bookmarklet public around the time of the Firefox 1.5 release. * Before I release the "Stir DOM" bookmarklet, it would be nice if a Firefox release immune to the easy-to-find, exploitable crashes had already been released.
OK, I'll see what I can do...
Flags: blocking1.8b5?
Flags: blocking1.8b5? → blocking1.8b5+
If you come up with a very safe fix in the next couple of days, please request approval for the patch and we'll evaluate.
Flags: blocking1.8b5+ → blocking1.8b5-
Assignee: general → bzbarsky
Fixed by checkin for bug 278472.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Flags: testcase+
Whiteboard: fixed by bug 278472
Keywords: fixed1.8
Whiteboard: fixed by bug 278472 → [sg:critical?]fixed by bug 278472
Group: security
Summary: StirDOM/SVG crash [@ nsContentIterator::NextNode] → SVG crash [@ nsContentIterator::NextNode]
Flags: in-testsuite+ → in-testsuite?
Crash Signature: [@ nsContentIterator::NextNode]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: