839086 - In about:memory, blame detached windows on their opener

Status: RESOLVED INCOMPLETE

(Toolkit :: about:memory, defect)

Description

[Justin Lebar (not reading bugmail)]

We currently stick all detached windows in a global bucket in about:memory.

But khuey realized that we can do better than this by merely walking the window.parent/opener chain!

Actually, it's not that simple, because if you remove an iframe from the document, its parent becomes null.  So we'd just have to record the old parent at some point (e.g. when we create the window).

Popup windows have a similar problem: You can null out window.opener.  We can either handle this the same way as we handle parent, or we can ignore this, because most page probably won't null out opener.

Comment 1

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

I don't think I'm going to do this anytime soon.

Comment 2

[Karl Crank]

Getting the same issues too and here's a screenshot of my specs http://bit.ly/3i4cSai that I uploaded but I guess its not going to be resolved anytime soon.

Comment 3

[Andrew McCreight [:mccr8]]

I don't think this is particularly worth leaving open. I don't think detached windows are a huge deal, and in the Fission era I don't know if the useful information will all be in the same process anyways.