Open
Bug 1178651
Opened 9 years ago
Updated 2 years ago
Consider sharing the self-hosting compartment from chrome to content processes
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox42 | --- | affected |
People
(Reporter: till, Unassigned)
Details
(Whiteboard: [MemShrink:P2])
Bill and I talked about this on the bus ride from Whistler. The self-hosting compartment is frozen after initialization and shared across all threads in a process. It might be feasible to extend this to also share it across all content processes. The zone for the self-hosting compartment is currently 228kb (about 40kb of which is in unused GC things, btw), so this might not be worth it for a single content process. In a process-per-tab configuration, however, it'd probably make sense.
|
||
Updated•9 years ago
|
Whiteboard: [MemShrink?] → [MemShrink:P2]
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•