425546 - Firefox leaks when i have a bunch of tabs open and i open a new Window

Status: RESOLVED INCOMPLETE

(Core :: General, defect)

Description

[Carsten Book [:Tomcat]]

Attachment: leak gauge output

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5

Steps to reproduce:
-> 5 Tabs open:
* Firefox Firstrun: http://en-us.www.mozilla.com/en-US/firefox/3.0b5/firstrun/
* Default Startpage
* Leak Gauge Log Upload Site http://mxr.mozilla.org/mozilla/source/tools/footprint/leak-gauge.html
* litmus.mozilla.org and
* http://www.heise.de/newsticker/ 
-> i was reading through the testcases in Litmus when i have open a new Window and after this is closed Firefox

Thinks like: Leaked content nodes associated with node info manager at address 248c8c0.
 ... with document URI "http://heisebanner.geizhals.at/bigbtn".

Seems to be a banner/advertisement from one of the sites that were loaded.

Summary:
Leaked 47 out of 71 DOM Windows
Leaked 48 out of 82 documents
Leaked 24 out of 24 docshells
Leaked content nodes in 54 out of 88 documents

Comment 1

[Damon Sicore (:damons)]

+'ing this for investigation.  Jonas, can you please take a look?

Comment 2

[Olli Pettay [:smaug][[e-mail]]]

So far I haven't been able to reproduce this.
Tried few things like closing FF immediately after opening the new window
or waiting a bit to get one cycle collection before closing etc.
Tomcat, is this easily reproduceable?

Comment 3

[Olli Pettay [:smaug][[e-mail]]]

Tested also with leak gauge, still no leaks.

With 64bit-optimized-Linux-build
Summary:
Leaked 0 out of 28 DOM Windows
Leaked 0 out of 62 documents
Leaked 0 out of 12 docshells
Leaked content nodes within 0 out of 69 documents

With 32bit-debug-Linux-build
Summary:
Leaked 0 out of 39 DOM Windows
Leaked 0 out of 75 documents
Leaked 0 out of 15 docshells
Leaked content nodes within 0 out of 84 documents

With 32bit-optimized-Linux-build
Summary:
Leaked 0 out of 33 DOM Windows
Leaked 0 out of 70 documents
Leaked 0 out of 13 docshells
Leaked content nodes within 0 out of 79 documents

As can be seen from the total count of windows/docs/docshells, the original
test had more pages loaded during testing.
Would be great to find some reliable way to reproduce the leaks.

Comment 4

[Damon Sicore (:damons)]

Taking this off the blocking list as evidently it cannot be reproduced.  Tomcat, please re-nom if you find this again.

Comment 5

[Andrew McCreight [:mccr8]]

Filter on QUANTUMLEAK