932900 - (chromeyfix) Automatically fix Chrome -> Chrome window leaks

Status: NEW

(Core :: DOM: Core & HTML, defect, P5)

Description

[Andrew McCreight [:mccr8]]

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.

Comment 1

[Bobby Holley (:bholley)]

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.

Comment 2

[Nicholas Nethercote [inactive]]

What kinds of leaks would this fix?  What kinds of leaks would it not fix?

Comment 3

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

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.

Comment 4

[Bobby Holley (:bholley)]

(In reply to Kyle Huey [:khuey] ([e-mail]) 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?

Comment 5

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.