Closed
Bug 397704
Opened 17 years ago
Closed 17 years ago
Crash [@ nsSVGEnum::SetBaseValue]
Categories
(Core :: SVG, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jruderman, Assigned: longsonr)
References
Details
(4 keywords, Whiteboard: [sg:critical?])
Crash Data
Attachments
(1 file, 2 obsolete files)
67 bytes,
image/svg+xml
|
Details |
Loading the testcase crashes Firefox, making nsSVGEnum::SetBaseValue dereference 0xaaaaaaa1. Regression from bug 383685, perhaps?
Flags: blocking1.9?
Reporter | ||
Updated•17 years ago
|
Whiteboard: [sg:critical?]
Reporter | ||
Comment 1•17 years ago
|
||
The crash is preceded by: ###!!! ASSERTION: mapping request for a non-attrib enum: 'info.mEnumCount > 0 && mAttrEnum < info.mEnumCount', file /Users/jruderman/trunk/mozilla/content/svg/content/src/nsSVGEnum.cpp, line 56
Assignee | ||
Comment 2•17 years ago
|
||
Assignee | ||
Comment 3•17 years ago
|
||
Attachment #282514 -
Attachment is obsolete: true
Attachment #282521 -
Flags: review?(tor)
Attachment #282514 -
Flags: review?(tor)
How I hate <marker>'s orient... This will stop a crash, but calling SetOrientToAuto or SetOrientToAngle won't cause the marker top update (not that it would have done so before either).
Assignee | ||
Comment 5•17 years ago
|
||
(In reply to comment #4) > How I hate <marker>'s orient... > > This will stop a crash, but calling SetOrientToAuto or SetOrientToAngle won't > cause the marker top update (not that it would have done so before either). > Well, bug 397749 will fix those although at the moment that patch has this fix and bug 397620 in it.
Attachment #282521 -
Flags: review?(tor) → review+
Assignee | ||
Updated•17 years ago
|
Attachment #282521 -
Flags: superreview?(roc)
Gah! Having nsSVGEnumMapping change over time for the same element is a bit of a trap since none of the others do that. How hard would it be to leave it the same but have extra code elsewhere to deal with the orient?
Assignee | ||
Updated•17 years ago
|
Attachment #282521 -
Attachment is obsolete: true
Attachment #282521 -
Flags: superreview?(roc)
Assignee | ||
Comment 7•17 years ago
|
||
The patch in bug 397749 fixes this crash, together with a number of other issues. For orientType the nsSVGEnumMapping does not change over time, it does not exist at all. I've now made a special SetBaseValue method that only nsSVGMarkerElement can use for enumerations to handle orientType. nsSVGEnum.cpp file no longer requires changes.
Assignee | ||
Comment 8•17 years ago
|
||
Fixed by check in for bug 397749
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 9•17 years ago
|
||
Reopening as the patch for bug 397749 has been backed out.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 10•17 years ago
|
||
bug 397749 has been checked in again.
Status: REOPENED → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → FIXED
Updated•17 years ago
|
Flags: in-testsuite?
Reporter | ||
Comment 11•16 years ago
|
||
Loading the testcase does not cause any assertions or crash on branch.
Group: security
Flags: wanted1.8.1.x-
Updated•13 years ago
|
Crash Signature: [@ nsSVGEnum::SetBaseValue]
You need to log in
before you can comment on or make changes to this bug.
Description
•