405169 - Creating a secondary window leaks (3 memory leakages)

Status: RESOLVED WORKSFORME

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

Description

[Gérard Talbot]

The webpage creates a secondary window with window.open() and loads a rather empty document (PopupWindowOnlyImage.html) and then populates it with data (url, dimensions, etc) defined, specified in the opener webpage. Global variables (opener.glbVariables; eg gblImgWidth) are used to achieve a "bridge" between secondary window and opener window.

Initial conditions:
-------------------
Make sure you have D. Baron's Leak Monitor 0.3.6 installed
https://addons.mozilla.org/firefox/2490/
http://dbaron.org/mozilla/leak-monitor/

Steps to reproduce:
-------------------
1- Load provided URL
2- Click one of the 3 links, say, the Olivia-Newton John one
3- Once fully loaded, close the created secondary window
(clicking the upper right X button or Alt+F4 or with Alt+Space bar, then scrolling down to Close in the system command menu of the window)

Actual results in Firefox 2.0.0.9 rv:1.8.1.9 build 20071025:
3 leakages are reported

Reproducible: always

Expected results: 
no leakage reported

Notes:
- I can copy and paste in here the reports or attach the reports to this bug
- I have not tested with a nightly trunk build

Comment 1

[Jo Hermans]

no leak on the trunk
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b2pre) Gecko/2007112605 Minefield/3.0b2pre

Comment 2

[Gérard Talbot]

Jo,

I downloaded and installed Minefield/3.0b2pre rv:1.9b2pre) Gecko/2007112605, tried to install D. Baron's Leak Monitor 0.3.6 but couldn't as it was impossible to install for that nightly build. So, I wondered what made you say there were no memory leakages for the provided URL.

Please understand me right. I'm not questioning your findings. I'm wondering which tool you used (and where you got it) so that I could use that same tool and then report memory leakages.

Comment 3

[Jo Hermans]

I just set the following environment variables

set NSPR_LOG_MODULES=DOMLeak:5,DocumentLeak:5,nsDocShellLeak:5
set NSPR_LOG_FILE=leaklog.log

And run the testcase. I use the Nightly Tester Tools to analyze the logfile (similar to leak-gauge).

See <http://wiki.mozilla.org/Performance:Leak_Tools> for more information on the various testtools that are being used.

PS : you can use the Nightly Tester Tools to load LeakMonitor.

Comment 4

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

Can you test if this still leaks in firefox 3 beta 2? We've done a lot of work on leaks and chances are it's fixed there.

Comment 5

[Gérard Talbot]

Jonas and Jo: I have not used the leak tools (Nightly Tester Tools and LeakMonitor). I now use Firefox 3 only and somewhat forgot about this bug. Thank you for your information and your assistance.

Resolving as WORKSFORME