Open Bug 866242 Opened 11 years ago Updated 2 years ago

Parent process window leak if content process crashes or is destroyed while it has a pending browser-API DOM request

Categories

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

defect

Tracking

()

People

(Reporter: justin.lebar+bug, Unassigned)

References

Details

(Whiteboard: [MemShrink:P3])

I haven't experimentally verified this leak, but I'm pretty sure it happens. BrowserElementParent.jsm keeps a list of outstanding DOMRequests. If a frame crashes while it has an outstanding DOMRequest, we'll never release the request. This is bad, because we should fire onfailure. But it's worse because the request holds a reference to the owner of the frame that just died, so we'll permanently leak that window (I think).
Whiteboard: [MemShrink]
Summary: Parent process window leak if content process crashes or is destroyed while it has a pending DOM request → Parent process window leak if content process crashes or is destroyed while it has a pending browser-element DOM request
Whiteboard: [MemShrink] → [MemShrink:P3]
Summary: Parent process window leak if content process crashes or is destroyed while it has a pending browser-element DOM request → Parent process window leak if content process crashes or is destroyed while it has a pending browser-API DOM request
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
Component: DOM → DOM: Core & HTML
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.