Closed Bug 669025 Opened 9 years ago Closed 9 years ago

"ASSERTION: Class name and proto chain interface name mismatch!"

Categories

(Core :: SVG, defect)

x86_64
macOS
defect
Not set

Tracking

()

RESOLVED FIXED
mozilla7

People

(Reporter: jruderman, Assigned: longsonr)

References

(Blocks 1 open bug)

Details

(Keywords: assertion, regression, testcase)

Attachments

(3 files, 2 obsolete files)

Attached image testcase
###!!! ASSERTION: Class name and proto chain interface name mismatch!: 'nsCRT::strcmp(CutPrefix(name), mData->mName) == 0', file /builds/slave/m-cen-osx64-dbg/build/dom/base/nsDOMClassInfo.cpp, line 4930

The first bad revision is:
changeset:   6ef387126d0f
user:        Robert Longson
date:        Fri Jul 01 08:19:52 2011 +0100
summary:     Bug 617623 - animate number-optional-number and integer-optional-integer attributes properly. r=dholbert
Attached file stack trace
Attached patch patch (obsolete) — Splinter Review
Assignee: nobody → longsonr
Attachment #543662 - Flags: review?(dholbert)
Comment on attachment 543662 [details] [diff] [review]
patch

Could you include crashtests for both changes? (both the Integer & Number varieties)
Attachment #543662 - Flags: review?(dholbert) → review+
Attached patch hg changeset patch with tests (obsolete) — Splinter Review
Attachment #543662 - Attachment is obsolete: true
Keywords: checkin-needed
Ms2ger pushed this to m-i, but it caused orange due to typo in crashtest.list manifest.

It needs s/669205/669025/

I don't have a local m-i repo or I'd fix it.  I'll try to get one over my current veryslow internet connection, but if anyone else can fix it before I do, please do.
Attached patch fix typoSplinter Review
Attachment #543692 - Attachment is obsolete: true
Thanks Phil. Kind of you.
http://hg.mozilla.org/mozilla-central/rev/450aec0642c3
http://hg.mozilla.org/mozilla-central/rev/58b34369196f
Status: NEW → RESOLVED
Closed: 9 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → mozilla7
Flags: in-testsuite+
You need to log in before you can comment on or make changes to this bug.