Bug 932900 (chromeyfix)

Automatically fix Chrome -> Chrome window leaks

NEW
Unassigned

Status

()

Core
DOM
5 years ago
4 years ago

People

(Reporter: mccr8, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [MemShrink:P2])

(Reporter)

Description

5 years ago
This is a followup to bug 695480.  Kyle points out that we should fix this for Chrome -> Chrome leaks.  Bug 932867 and bug 932880 are examples of this.
IIRC kyle originally had this working, but it went bright-orange with CPG, and he decided it wasn't worth the effort at the time.
What kinds of leaks would this fix?  What kinds of leaks would it not fix?
Flags: needinfo?(khuey)
It would fix leaks where chrome JSMs/js components/windows reference objects in closed chrome windows.  It would not fix leaks where chrome JSMs/js components/windows reference objects in chrome windows that are still in the DOM somewhere, such as iframes in the hidden window.
Flags: needinfo?(khuey)
(In reply to Kyle Huey [:khuey] (khuey@mozilla.com) from comment #3)
> It would fix leaks where chrome JSMs/js components/windows reference objects
> in closed chrome windows.  It would not fix leaks where chrome JSMs/js
> components/windows reference objects in chrome windows that are still in the
> DOM somewhere, such as iframes in the hidden window.

Given our newfangled usage of this stuff with Sandbox.jsm, could we add a special-case for that stuff somehow?
Whiteboard: [MemShrink] → [MemShrink:P2]
You need to log in before you can comment on or make changes to this bug.