Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1) Gecko/20060920 BonEcho/2.0 ID:2006092004 1. New profile, start firefox with leak logging 2. Paste http://search.msn.com/results.aspx?q=test&FORM=MSNH in the URL bar and hit enter 3. After page has loaded, close firefox. 4. Use leak-gauge.pl to analyse the NSPR.log Leaked outer window 2469d00 at address 2469d00. Leaked inner window 2b0acf0 (outer 2469d00) at address 2b0acf0. ... with URI "http://search.msn.co.uk/results.aspx?q=test&geovar=70&FORM=REDIR" . Leaked document at address 1b99528. ... with URI "http://search.msn.co.uk/results.aspx?q=test&geovar=70&FORM=REDIR" . Summary: Leaked 2 out of 8 DOM Windows Leaked 1 out of 37 documents Leaked 0 out of 3 docshells

Alternative: 1. New profile, start firefox with leak logging 2. Go to http://www.live.com/ , enter a search term, then initiate the search 3. After page has loaded, close firefox. 4. Use leak-gauge.pl to analyse the NSPR.log

Can you test this with current trunk? I know dbaron's landed two patches recently that were supposed to fix leaks.

I'd love to, except Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/2006092104 Minefield/3.0a1 hangs on shutdown (99% CPU) so I can't get a clean log to analyse. (With a new profile, naturally)

FWIW, my trunk builds hang on shutdown, too, but I'm still able to get leak data from them. Using the steps to reproduce in comment 0 and comment 1, I verified that this leak got fixed on trunk between 2006-09-19-04 and 2006-09-20-04. That's when dbaron's patch for bug 353090 landed, so I'm assuming that fixed the leak. dbaron, were you planning on getting that patch in on branch?

> dbaron, were you planning on getting that patch in on branch? Is it relevant to the branch? It looked like a trunk DOM_AGNOSTIC regression to me... but maybe I'm wrong.

That one isn't, actually. See bug 353090 comment 2.

The patch for the 1.8 branch will look very different, but I am planning to write it... Is there a bug on the builds hanging on shutdown?

Yes, it's either bug 341384 or bug 338884.

*** This bug has been marked as a duplicate of 353090 ***