Closed
Bug 885769
Opened 11 years ago
Closed 11 years ago
Assertion failure: cxArg, at dist/include/js/RootingAPI.h
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: gkw, Assigned: shu)
References
Details
(Keywords: assertion, regression, testcase, Whiteboard: [fuzzblocker])
Attachments
(1 file)
2.35 KB,
text/plain
|
Details |
ParallelArray(4277, (function() {})) asserts a threadsafe js debug shell on m-c changeset 61c3c8b85563 with --ion-parallel-compile=on at Assertion failure: cxArg, at dist/include/js/RootingAPI.h
Reporter | ||
Comment 1•11 years ago
|
||
autoBisect shows this is probably related to the following changeset: The first bad revision is: changeset: http://hg.mozilla.org/mozilla-central/rev/ce7085b63b2b user: Bobby Holley date: Thu Jun 20 11:05:34 2013 -0700 summary: Bug 883450 - Assert that we're in a request whenever we create a Rooted<T>. r=terrence
Blocks: 883450
Flags: needinfo?(bobbyholley+bmo)
Reporter | ||
Comment 3•11 years ago
|
||
Due to its simplicity, actually this is causing a lot of trouble (assorted crash signatures, etc.) in jsfunfuzz.
Whiteboard: [fuzzblocker]
Comment 4•11 years ago
|
||
It looks like the PJS code is passing null to the Rooted Constructor.
Assignee | ||
Comment 5•11 years ago
|
||
This is more than a simple unrooting, in that right now we assume that there is a JSContext available for use inside ParallelArrayAnalysis for operations such as making new template objects while replacing MIR nodes. I'm working on a patch to separate ParallelArrayAnalysis into 2 phases, one that might potentially need a JSContext, and one that doesn't. If I can't get that patch done by tonight I'll post a temporary patch for this bug.
Assignee | ||
Updated•11 years ago
|
Flags: needinfo?(nmatsakis)
Assignee | ||
Comment 6•11 years ago
|
||
If fixes for bug 886632 and bug 887002 stick, this will be fixed.
Assignee | ||
Updated•11 years ago
|
Assignee: general → shu
Assignee | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•