Closed Bug 819723 Opened 12 years ago Closed 3 days ago

IonMonkey: Don't bailout on cross-compartment calls.

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86_64
Linux
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: nbp, Unassigned)

References

Details

With a patch for Bug 803710, I obtain the following error message $ IONFLAGS=aborts ./_build/js-bug803710-dbg-x64-gcc45 --ion-crash-on-unexpected-disable --no-jm ./jit-test/tests/basic/testBug723445.js [Abort] eval frame [Abort] Disabling Ion compilation of script ./jit-test/tests/basic/testBug723445.js:2 [Abort] Ion frequent bailout loop @ bytecode: call, MIR: call , LIR: callgeneric which is caused by more than 20 consecutive and frequent bailout at the same location.
Assignee: general → nobody
Severity: normal → S3

Still relevant now?

We have robust bailout loop detection now.

Also, I'm not aware of any code that would cause us to bail out on cross-compartment calls.

Status: NEW → RESOLVED
Closed: 3 days ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.