Open
Bug 941794
Opened 11 years ago
Updated 2 years ago
Enable incremental GC for DOM workers
Categories
(Core :: JavaScript: GC, defect)
Core
JavaScript: GC
Tracking
()
NEW
People
(Reporter: mccr8, Unassigned)
References
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.
|
||
Comment 1•11 years ago
|
||
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).
|
||
Updated•11 years ago
|
Whiteboard: [Games][Shumway
|
|
||
Comment 2•11 years ago
|
||
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]
|
||
Updated•11 years ago
|
Component: JavaScript Engine → JavaScript: GC
Whiteboard: [Games][Shumway] → [Games] [shumway:m2]
|
|
||
Updated•10 years ago
|
Blocks: shumway-1.0
Whiteboard: [Games] [shumway:m2] → [Games] [shumway]
|
|
||
Updated•10 years ago
|
No longer blocks: shumway-1.0
Whiteboard: [Games] [shumway] → [Games]
|
||
Updated•2 years ago
|
Severity: normal → S3
|
||
Updated•2 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•