Open
Bug 932900
(chromeyfix)
Opened 11 years ago
Updated 2 years ago
Automatically fix Chrome -> Chrome window leaks
Categories
(Core :: DOM: Core & HTML, defect, P5)
Core
DOM: Core & HTML
Tracking
()
NEW
People
(Reporter: mccr8, Unassigned)
References
Details
(Whiteboard: [MemShrink:P2])
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•11 years ago
|
||
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•11 years ago
|
||
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)
Comment 4•11 years ago
|
||
(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?
Updated•11 years ago
|
Whiteboard: [MemShrink] → [MemShrink:P2]
Comment 5•6 years ago
|
||
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.
Priority: -- → P5
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•