Closed
Bug 786465
Opened 12 years ago
Closed 3 years ago
Octane's Mandreel benchmark trips alert
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
INACTIVE
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.
Reporter | ||
Comment 1•12 years ago
|
||
Runs correctly with tip from m-c.
Reporter | ||
Updated•12 years ago
|
Summary: IonMonkey: Octane's Mandreel benchmark trips alert with --no-ion → IonMonkey: Octane's Mandreel benchmark trips alert
Reporter | ||
Comment 2•12 years ago
|
||
Only reproduces in opt builds.
Reporter | ||
Comment 3•12 years ago
|
||
(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.
Reporter | ||
Updated•12 years ago
|
Summary: IonMonkey: Octane's Mandreel benchmark trips alert → Octane's Mandreel benchmark trips alert
Updated•12 years ago
|
Whiteboard: [js:t]
Assignee | ||
Updated•10 years ago
|
Assignee: general → nobody
Updated•3 years ago
|
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•