This leak exploded this morning on mozilla-inbound, and I wanted to pin it on the push after a merge from mozilla-central, because the merge was green and the next push had three instances of this leak, but I didn't have time during the day, and then bugmail about this same leak being misstarred as a crashtest leak alerted me that it was on mozilla-central before my blame-target had gotten there. First seen on mozilla-central on https://hg.mozilla.org/mozilla-central/rev/1cdef0321abd (merge from fx-team), first seen on fx-team on https://hg.mozilla.org/integration/fx-team/rev/29c4463e6a2e (enable New Tab Page and what I presume are supporters, which are just as likely to be the real cause I suppose). Retriggers in https://tbpl.mozilla.org/?tree=Fx-Team&rev=29c4463e6a2e show plenty more instances beside the one that was there from the initial push; retriggers on the parent in https://tbpl.mozilla.org/?tree=Fx-Team&rev=e7f7c1e948ca don't show any (gambling, because I still have a couple of retriggers running right this second, but the odds are with me). Sorry, but, j'accuse. http://tbpl.swatinem.de/php/getLeakAnalysis.php?id=9053424 (the working version of the "analyze the leak" links that are broken on tbpl.m.o) only mentions the lying not actually leaked domwindow from test_process_error.xul, so unfortunately there's no help about which test is triggering the leak, other than "something in browser-chrome" (and "not test_process_error.xul, which isn't even in browser-chrome").

https://tbpl.mozilla.org/php/getParsedLog.php?id=9049357&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=9050675&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=9050853&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=9045027&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=9042171&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=9044949&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=9045241&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=9040562&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=9034825&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=9034134&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=9034857&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=9047572&tree=Mozilla-Inbound

https://tbpl.mozilla.org/php/getParsedLog.php?id=9062661&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=9067725&tree=Mozilla-Inbound

https://tbpl.mozilla.org/php/getParsedLog.php?id=9068364&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=9068265&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=9068623&tree=Mozilla-Inbound

I'm optimistic about this being fixed by bug 723102 - we accidentally hold New Tab Pages alive by the JSM (instead of properly unregistering them). Will land today.

https://tbpl.mozilla.org/php/getParsedLog.php?id=9097451&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=9097603&tree=Mozilla-Inbound

Marking as fixed by bug 723102.

https://tbpl.mozilla.org/php/getParsedLog.php?id=9230791&tree=Mozilla-Aurora (a couple of pushes after you flipped the pref on aurora) reminds me a great deal of this, so I think you might have had another thing involved in the leak fix, that didn't hit aurora.

(In reply to Phil Ringnalda (:philor) from comment #28) > https://tbpl.mozilla.org/php/getParsedLog.php?id=9230791&tree=Mozilla-Aurora > (a couple of pushes after you flipped the pref on aurora) reminds me a great > deal of this, so I think you might have had another thing involved in the > leak fix, that didn't hit aurora. Yeah, but I don't have a clue what changeset fixed that entirely. Need to look what landed around the same time.

https://tbpl.mozilla.org/php/getParsedLog.php?id=10084544&tree=Mozilla-Inbound Sure was nice having this gone for a while, back when it was gone for a while.

Nominating for tracking because it is a fairly large, fairly frequent leak apparently introduced by a new feature.

(In reply to Andrew McCreight [:mccr8] from comment #60) > Nominating for tracking because it is a fairly large, fairly frequent leak > apparently introduced by a new feature. This is reasonable - also sending over to Tim since we suspect this to be related to the new tab page.

https://tbpl.mozilla.org/php/getParsedLog.php?id=10765719&tree=Mozilla-Aurora https://tbpl.mozilla.org/php/getParsedLog.php?id=10765563&tree=Mozilla-Aurora

What's happening here? This is a significant leak in a new feature.

(In reply to Tim Taubert [:ttaubert] from comment #38) > (In reply to Phil Ringnalda (:philor) from comment #28) > > https://tbpl.mozilla.org/php/getParsedLog.php?id=9230791&tree=Mozilla-Aurora > > (a couple of pushes after you flipped the pref on aurora) reminds me a great > > deal of this, so I think you might have had another thing involved in the > > leak fix, that didn't hit aurora. > > Yeah, but I don't have a clue what changeset fixed that entirely. Need to > look what landed around the same time. This appears to still be a problem on FF13 and up. What are the next steps for this investigation?

I'm kind of hoping that this was fixed by bug 750424. It hasn't happened on inbound since that patch landed, but with the tree closed there haven't been enough pushes to say for sure.

I'm going to call this fixed.

https://tbpl.mozilla.org/php/getParsedLog.php?id=11696918&tree=Mozilla-Beta https://tbpl.mozilla.org/php/getParsedLog.php?id=11704666&tree=Mozilla-Beta

(In reply to Bill McCloskey (:billm) from comment #150) > I'm kind of hoping that this was fixed by bug 750424. It hasn't happened on > inbound since that patch landed, but with the tree closed there haven't been > enough pushes to say for sure. We'll track bug 750424 instead in that case. Thanks!