Closed Bug 777184 Opened 12 years ago Closed 5 years ago

IonMonkey: OOM Testing: Crash [@ js::ion::MBasicBlock::setLoopDepth]

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Version:
Other Branch
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: decoder, Unassigned)

References

Details

(Keywords: crash, testcase, Whiteboard: [ion:t])

Crash Data

The following command crashes on ionmonkey revision b82fb4d04f60 (dbg build):

js  -e 'const libdir = "js/src/jit-test/lib/";' -A 15022 -f js/src/jit-test/tests/v8-v5/check-richards.js
Assignee: general → nobody
Closing because no crash reported since 12 weeks.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Closing because no crash reported since 12 weeks.
Reopening because crash bugs **with testcases** should not be resolved **as WONTFIX** based on queries of crash-stats.  Other resolutions may be appropriate for other reasons.

(Crash signatures are not the same as bug identity; they're merely a search aid to find and group similar crashes.  The bug may still be present, but the signature may have changed slightly, or the bug may even still be present with the same signature but there are simply no recent reports of crashes in that function.)
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Iain, do you think this old IonMonkey OOM issue is still valid?
Flags: needinfo?(iireland)
This fails to replicate. Even better, we can be pretty confident that it was fixed at some point.

MBasicBlock::setLoopDepth is a straightforward setter. The only way it could possibly crash is by calling it on a null pointer. There are only 8 places where we call setLoopDepth in the current codebase, and they all check for null pointers at some point before calling setLoopDepth.

Closing as WORKSFORME.
Status: REOPENED → RESOLVED
Closed: 6 years ago → 5 years ago
Flags: needinfo?(iireland)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.