Closed
Bug 858077
Opened 12 years ago
Closed 12 years ago
Assertion failure: !unknownObject(), at ../jsinferinlines.h:1519 with ParallelArray
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
mozilla23
People
(Reporter: decoder, Assigned: nmatsakis)
Details
(Keywords: assertion, testcase, Whiteboard: [jsbugmon:update])
Attachments
(1 file)
1.32 KB,
patch
|
bhackett1024
:
review+
|
Details | Diff | Splinter Review |
The following testcase asserts on mozilla-central revision c232bec6974d (no options required):
var a = new ParallelArray([1,2,3,4]);
for (var i = 0; i < 9 && i > -1000; i-- )
a[i] += [0];
Reporter | ||
Updated•12 years ago
|
Whiteboard: [jsbugmon:update,bisect]
Reporter | ||
Updated•12 years ago
|
Whiteboard: [jsbugmon:update,bisect] → [jsbugmon:update]
Reporter | ||
Comment 1•12 years ago
|
||
JSBugMon: Bisection requested, result:
autoBisect shows this is probably related to the following changeset:
The first bad revision is:
changeset: 127434:e5978106c61a
parent: 127433:280e5ed3f0b7
parent: 125575:1d6fe70c79c5
user: Jan de Mooij
date: Thu Mar 21 11:23:12 2013 +0100
summary: Merge from mozilla-central.
Not all ancestors of this changeset have been checked.
Use bisect --extend to continue the bisection from
the common ancestor, 0bba6ba92467.
This iteration took 146.421 seconds to run.
Oops! We didn't test rev 1d6fe70c79c5, a parent of the blamed revision! Let's do that now.
Rev 1d6fe70c79c5: Found cached shell... Testing... [Uninteresting] It didn't crash. (0.232 seconds)
good (not interesting)
As expected, the parent's label is the opposite of the blamed rev's label.
Assignee | ||
Comment 2•12 years ago
|
||
Attachment #733911 -
Flags: review?(bhackett1024)
Assignee | ||
Updated•12 years ago
|
Assignee: general → nmatsakis
Updated•12 years ago
|
Attachment #733911 -
Flags: review?(bhackett1024) → review+
Assignee | ||
Comment 3•12 years ago
|
||
Comment 4•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla23
You need to log in
before you can comment on or make changes to this bug.
Description
•