Consider sharing the self-hosting compartment from chrome to content processes

NEW
Unassigned

Status

()

Core
JavaScript Engine
3 years ago
3 years ago

People

(Reporter: till, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(firefox42 affected)

Details

(Whiteboard: [MemShrink:P2])

(Reporter)

Description

3 years ago
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.
Whiteboard: [MemShrink?] → [MemShrink:P2]
You need to log in before you can comment on or make changes to this bug.