Closed Bug 1199227 Opened 9 years ago Closed 9 years ago

OOM simulation doesn't distinguish between threads

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1199203

People

(Reporter: jonco, Unassigned)

Details

OOM simulation triggered by oomAtAllocation() or oomAfterAllocation() doesn't distinguish between the main thread and background threads which makes OOM testing non-deterministic if threads are used.

A solution would probably have to allocating OOM_counter in thread-local storage, which might have performance implications.  This is debug-only though.

We could then make the aforementioned JS functions take a parameter to say whether to cause OOM failures on the main thread or a background thread.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.