Closed
Bug 835496
Opened 13 years ago
Closed 13 years ago
IonMonkey: "Assertion failure: !val.isMagic()," or "Assertion failure: data.s.payload.why == why,"
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
mozilla21
People
(Reporter: gkw, Assigned: bhackett1024)
References
Details
(Keywords: assertion, regression, testcase, Whiteboard: [jsbugmon:update])
Attachments
(2 files)
12.03 KB,
text/plain
|
Details | |
1.15 KB,
patch
|
jandem
:
review+
|
Details | Diff | Splinter Review |
(function([{x}]) {})({
t: 0,
"1": 0
})
asserts js debug shell on m-c changeset 80fed51ae074 with --ion-eager at Assertion failure: !val.isMagic(),
(function([[x]]) {})({
t: 0,
"1": 0
})
asserts js debug shell on m-c changeset 80fed51ae074 with --ion-eager at Assertion failure: data.s.payload.why == why,
(both point to bug 832364)
autoBisect shows this is probably related to the following changeset:
The first bad revision is:
changeset: 119980:e6d6b014a076
parent: 119968:d802d6faa080
user: Brian Hackett
date: Sat Jan 26 13:21:27 2013 -0700
summary: Bug 832364 - Generate optimized paths for element accesses on native objects, r=jandem.
![]() |
Reporter | |
Comment 1•13 years ago
|
||
Brian, is bug 832364 the likely regressor?
Flags: needinfo?(bhackett1024)
Assignee | ||
Comment 2•13 years ago
|
||
This bug was exposed by bug 832364, but it's actually a regression from bug 827490. When we encounter object literals in global code we change their type according to what properties they have, but were totally ignoring any dense elements on the objects so that their type information was incorrect.
Assignee: general → bhackett1024
Attachment #707594 -
Flags: review?(jdemooij)
Flags: needinfo?(bhackett1024)
Updated•13 years ago
|
Attachment #707594 -
Flags: review?(jdemooij) → review+
Assignee | ||
Comment 3•13 years ago
|
||
![]() |
Reporter | |
Updated•13 years ago
|
Comment 4•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → mozilla21
You need to log in
before you can comment on or make changes to this bug.
Description
•