353658 - [mlk] at Adult Friend Finder --> Affiliates

Status: RESOLVED DUPLICATE of bug 353022

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

Description

[Steve England [:stevee]]

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. Go to http://www.adultfriendfinder.com/ (NOT WORK SAFE!)
3. Click on 'Affiliates' at the top, in the red bar.
3. After page has loaded, close firefox.
4. Use leak-gauge.pl to analyse the NSPR.log

Leaked document at address 28d5a90.
 ... with URI "chrome://browser/content/browser.xul".
Leaked document at address 28e8550.
 ... with URI "chrome://browser/content/browser.xul".
Leaked document at address 28f1008.
 ... with URI "chrome://browser/content/browser.xul".
Leaked document at address 28dacd8.
 ... with URI "chrome://browser/content/browser.xul".
Leaked document at address 28d7d48.
 ... with URI "chrome://browser/content/browser.xul".
Leaked document at address 2475d98.
 ... with URI "chrome://browser/content/browser.xul".
Summary:
Leaked 0 out of 8 DOM Windows
Leaked 6 out of 37 documents
Leaked 0 out of 3 docshells

Comment 1

[Steve England [:stevee]]

Exactly the same happens at cnet

1. New profile, start firefox with leak logging
2. Go to http://www.cnet.com/
3. Scroll to the bottom of the page and click on 'Jobs' (next to the About CNET Networks link in bold)
3. After page has loaded, close firefox.
4. Use leak-gauge.pl to analyse the NSPR.log

Leaked document at address 2988880.
 ... with URI "chrome://browser/content/browser.xul".
Leaked document at address 2973d38.
 ... with URI "chrome://browser/content/browser.xul".
Leaked document at address 297a270.
 ... with URI "chrome://browser/content/browser.xul".
Leaked document at address 29985f8.
 ... with URI "chrome://browser/content/browser.xul".
Leaked document at address 2989830.
 ... with URI "chrome://browser/content/browser.xul".
Leaked document at address 2984ff8.
 ... with URI "chrome://browser/content/browser.xul".
Summary:
Leaked 0 out of 18 DOM Windows
Leaked 6 out of 43 documents
Leaked 0 out of 7 docshells

Comment 2

[Adam Guthrie]

On trunk, both of these leaks were fixed between 2006-09-18-04 and 2006-09-19-04. So, I'm guessing the patch for bug 353022 fixed these.

Comment 3

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

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