Closed Bug 686178 Opened 8 years ago Closed 8 years ago

TI: Assertion failure: rejoin != REJOIN_NONE, at methodjit/Retcon.cpp:88

Categories

(Core :: JavaScript Engine, defect, critical)

x86_64
Linux
defect
Not set
critical

Tracking

()

RESOLVED FIXED

People

(Reporter: decoder, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: assertion, testcase, Whiteboard: fixed-in-jaegermonkey)

The following test asserts on jaegermonkey branch revision (options -m -n):


function assertSyntaxError(x) {
  try {
    new assertSyntaxError(x);
  } catch (e) {
    assertTrue(e instanceof SyntaxError, "is syntax error");
  }
};
assertSyntaxError("f(,)");
Forgot the revision: b31b25125429
Bogus assert (and recently added).  We can't rejoin from a call whose rejoin state is REJOIN_NONE, so asserted that we never marked a frame as having needing this rejoin due to recompilation activity within such a call.  If the recompilation is followed by (or a result of) throwing an exception, though, we won't be rejoining from the call and the written REJOIN_NONE will not be used.

http://hg.mozilla.org/projects/jaegermonkey/rev/a250c3cb749a
Whiteboard: js-triage-needed → fixed-in-jaegermonkey
https://hg.mozilla.org/mozilla-central/rev/c943bbf9dac4
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.