IonMonkey: Assertion failure: masm.framePushed() == 0, at ion/shared/CodeGenerator-x86-shared.cpp:111 with OOM

RESOLVED DUPLICATE of bug 777182

Status

()

--
major
RESOLVED DUPLICATE of bug 777182
6 years ago
6 years ago

People

(Reporter: decoder, Unassigned)

Tracking

(Blocks: 2 bugs, {assertion, testcase})

Other Branch
x86_64
Linux
assertion, testcase
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [jsbugmon:ignore][js:t])

Attachments

(1 attachment)

(Reporter)

Description

6 years ago
Created attachment 630556 [details]
Testcase for shell

The attached testcase asserts on ionmonkey revision ff28f1696c5a (run with --ion -n).
I can't seem to run the testcase.
Following instructions in the README produces:

[sstangl@mozdesk testMasmFramePushed]$ ~/dev/ionmonkey/js/src/dbg64/js --ion -n -f shell.js -f main.js
ReferenceError: jsTestDriverEnd is not defined
ReferenceError: jsTestDriverEnd is not defined
ReferenceError: jsTestDriverEnd is not defined
ReferenceError: jsTestDriverEnd is not defined
ReferenceError: jsTestDriverEnd is not defined
ReferenceError: reference to undefined XML name *::*
ReferenceError: jsTestDriverEnd is not defined
ReferenceError: g is not defined
ReferenceError: jsTestDriverEnd is not defined
9846ae0d6e2877fcbac6d0d51ae571f8c45399c7.js:96: out of memory
I can't reproduce this either with the given revision and instructions.
(Reporter)

Comment 3

6 years ago
What configure options did you use on the specified revision? I used --enable-debug --disable-optimize --enable-valgrind --enable-more-deterministic. The test does not reproduce for me on tip anymore, but I still see the assert on tip fuzzing results.
Whiteboard: [jsbugmon:update] → [jsbugmon:update,reconfirm]
(Reporter)

Updated

6 years ago
Whiteboard: [jsbugmon:update,reconfirm] → [jsbugmon:ignore]
Whiteboard: [jsbugmon:ignore] → [jsbugmon:ignore][js:t]
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 777182
You need to log in before you can comment on or make changes to this bug.