Closed Bug 864101 Opened 12 years ago Closed 12 years ago

Assertion failure: (*pvalue)->type() != propertyType, at ion/IonBuilder.cpp with bug 804676 fixes

Categories

(Core :: JavaScript Engine, defect)

x86_64
macOS
defect
Not set
critical

Tracking

()

RESOLVED FIXED
mozilla23

People

(Reporter: gkw, Assigned: bhackett1024)

References

Details

(Keywords: assertion, regression, testcase)

Attachments

(2 files)

Attached file stack (deleted) —
s = newGlobal(''); function g(code) { evalcx(code, s) } g("function f(){}"); g("a = x = f >>>= i"); asserts js debug shell on ionmonkey (where bug 804676 fixes landed for testing) changeset ae6a2cf914f7 with --no-baseline -a --ion-eager at Assertion failure: (*pvalue)->type() != propertyType, at ion/IonBuilder.cpp
Summary: Assertion failure: (*pvalue)->type() != propertyType, at ion/IonBuilder.cpp → Assertion failure: (*pvalue)->type() != propertyType, at ion/IonBuilder.cpp with bug 804676 fixes
Attached patch patch (deleted) — Splinter Review
This isn't a correctness assertion, but indicates in this case that a VM call is being made to capture type barriers when writing to a property that aren't necessary. When the input type to TypeSetIncludes is more precise than the input type set, the function inappropriately returns false.
Attachment #741792 - Flags: review?(dvander)
Attachment #741792 - Flags: review?(dvander) → review+
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla23
Assignee: general → bhackett1024
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: