Closed
Bug 1267441
Opened 9 years ago
Closed 8 years ago
Intermittent basic.js | uncaught exception: out of memory (code 3, args "--ion-eager --ion-offthread-compile=off --non-writable-jitcode --ion-check-range-analysis --ion-extra-checks --no-sse3 --no-threads")
Categories
(Core :: JavaScript Engine: JIT, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: KWierso, Unassigned)
References
Details
(Keywords: intermittent-failure)
|
||
Comment 1•9 years ago
|
||
Adding bbouvier and luke, because failure is in a wasm test: tests\jit-test\jit-test\tests\wasm\basic.js
|
||
Comment 2•9 years ago
|
||
Can't find a reason why it should fail here: there's a single test that is marked as being able to exhaust memory, but it's enclosed in a try/catch. The only wild guess I would make is that we somehow don't recover from this memory test, and then the next allocation fails somewhere else and we get an OOM. To test that, we could maybe move the OOM test at the end of the file, instead?
| Comment hidden (Intermittent Failures Robot) |
|
|
||
Comment 4•9 years ago
|
||
Interesting, it's win x64 only. Might have to deal with stack frame size? Or something specific to win x64 frames that we would have forgotten...
| Comment hidden (Intermittent Failures Robot) |
|
|
||
Comment 6•8 years ago
|
||
No intermittent filed for a month, marking as wfm.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•