Closed
Bug 736594
Opened 12 years ago
Closed 12 years ago
IonMonkey: "Assertion failure: actual.empty() && spilled.empty(),"
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: gkw, Unassigned)
References
Details
(Keywords: assertion, testcase)
Attachments
(1 file)
8.94 KB,
text/plain
|
Details |
The upcoming testcase asserts js debug shell on IonMonkey changeset b96587f04076 with -m, -a, --ion and -n at Assertion failure: actual.empty() && spilled.empty(), gc seems involved just by looking at the stack.
Comment 2•12 years ago
|
||
Could it be you forgot to add the testcase?
Reporter | ||
Comment 3•12 years ago
|
||
> Could it be you forgot to add the testcase?
It is attached, just that it is set to private because it still has major fuzzer components present. I've emailed them to David, Sean and Nicolas in case they can't see it.
Updated•12 years ago
|
Version: Trunk → Other Branch
Comment 4•12 years ago
|
||
Marking s-s by description (gc involved) and because the assertion seems to indicate some form of memory corruption.
Group: core-security
Reporter | ||
Comment 5•12 years ago
|
||
> Marking s-s by description (gc involved) and because the assertion seems to
> indicate some form of memory corruption.
Unable to reproduce even with original changeset. -> WFM & opening up.
Group: core-security
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•