Open Bug 786465 Opened 9 years ago Updated 4 years ago

Octane's Mandreel benchmark trips alert

Categories

(Core :: JavaScript Engine, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

People

(Reporter: sstangl, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [js:t])

Running the Mandreel benchmark from Octane v1 with default configuration or --no-ion gives the following alert instead of a result:

> Mandreel: Alert called with argument: Check sum mismatch: expected ???, actual 15298151

Running with --no-ion --no-jm does not reproduce. Additionally, it works in-browser.

Nicolas pointed out that the major difference between the browser and the shell is the code-preservation behavior: adding gcPreserveCode() to mandreel.js lets the test run successfully with any option configuration.
Runs correctly with tip from m-c.
Summary: IonMonkey: Octane's Mandreel benchmark trips alert with --no-ion → IonMonkey: Octane's Mandreel benchmark trips alert
Only reproduces in opt builds.
(In reply to Sean Stangl from comment #1)
> Runs correctly with tip from m-c.

Whoops, I forgot that m-c requires -m -n flags. With -m -n, it breaks on m-c in the same way.
Summary: IonMonkey: Octane's Mandreel benchmark trips alert → Octane's Mandreel benchmark trips alert
Whiteboard: [js:t]
Assignee: general → nobody
You need to log in before you can comment on or make changes to this bug.