Enable incremental GC for DOM workers

NEW
Unassigned

Status

()

defect
6 years ago
5 years ago

People

(Reporter: mccr8, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [Games])

One use case for DOM workers is to drive animations.  In that case, pauses are bad, so we'd want incremental GC.  I'd guess the main work here is ensuring that all of the custom-trace-hooked stuff is properly barriered.
This would undo the space savings from bug 921224, which reduced the size of the gc marker stack in JSRuntimes that don't use incremental GC (i.e. worker JSRuntimes, currently).
Whiteboard: [Games][Shumway
Highly relevant for Shumway, which is moving to a setup where (action)script execution happens on a worker thread, with rendering and compositing happening on the main thread.
Whiteboard: [Games][Shumway → [Games][Shumway]
Component: JavaScript Engine → JavaScript: GC
Whiteboard: [Games][Shumway] → [Games] [shumway:m2]
Blocks: shumway-1.0
Whiteboard: [Games] [shumway:m2] → [Games] [shumway]
No longer blocks: shumway-1.0
Whiteboard: [Games] [shumway] → [Games]
You need to log in before you can comment on or make changes to this bug.