642472 - Massive Memory Leak when using NoScript in Firefox 4

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[James]

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0

Discovered this memory leak while doing some work on a highway project and was wondering why FF4 RC1 was using so much more memory than when I was doing this in FF 3.6.15 before the upgrade.

Reproducible: Always

Steps to Reproduce:
0. Have at least NoScript installed first.
1. Load: http://cmap.m-plex.com/hb/hwymap.php?mt=g&r=ky.us031w&sys=usaus&rg=all&gr=&off=&showint=30
2. View each layer in this order: Mapnik (starting point) > Osmarend > CHM > Yahoo Map > Yahoo Aerial > Bing Map > Bing Arerial > Bing Hybrid > Map > Satellite > Hybrid > Terrain > (back to) Map
3. Pan around the USA twice (around the border) using the mouse in the big window.
4. "center" the map back at the starting point via the hand in the middle of the panning circle.
5. Zoom in all the way with the "Zoom In" (the "+") button.
6. Zoom all the way out using the "Zoom Out" (the "-") button.
7. Repeat Step 5.
8. Repeat Step 6.
9. Firefox should dump some memory. (wait about 1-2 minutes)
10. Hit the Recenter button so it's zoomed back in.
11. Do another two laps panning around the USA (like in step 3) and then recenter again.
Actual Results:  
Memory Usage by FF was off the charts.

Expected Results:  
Memory Usage should have been no more that 200,000K at any time during this (especially if it was the only tab open).  More reasonably no more that 150,000K if possible. (IE9 can do it with less than 60,000K of memory usage.)

http://forums.informaction.com/viewtopic.php?f=10&t=6019
At that link, I have the exact memory usage results of several different tests (Safe Mode, NS by itself, AB+ by itself and AB+ & NS together).  This also might be related to bug 639186.

Comment 1

[Giorgio Maone [:ma1]]

Couldn't reproduce on latest trunk.
Private bytes peaked around 500MB, then consistently went back under 200MB after forcing garbage collection.

Could you please retry with a recent nightly build? ftp://ftp.mozilla.org/pub/firefox/nightly/

You can speedup things, rather than waiting for Firefox to release memory automatically, by running the following snippet in your Error Console:

window.QueryInterface(Components.interfaces.nsIInterfaceRequestor)
      .getInterface(Components.interfaces.nsIDOMWindowUtils)
      .garbageCollect();

Comment 2

[videoclocknet]

James, can you grab a video of your desktop reproducing the issues and upload it?

I think we will understand better the steps you follow.

Comment 3

[James]

(In reply to comment #2)
> James, can you grab a video of your desktop reproducing the issues and upload
> it?
> 
> I think we will understand better the steps you follow.

Do you have any suggestion on what program I could use to capture a video?  I would use my camera, but I wouldn't be able to keep it steady and also run the test.  And then again, I just only want to record a part of my screen and not the whole thing.

Also, I noticed this bug (bug 637782) "might" be also related since Google does use a tile system for their map that has several images in it.  So, maybe if that bug is fixed, this one might go away too at least somewhat (of course I would test after that bug is fixed to verify).  So, if bug 637782 gets fixed, I'll see if this is fixed too, and if it isn't, I'll do that video thing.

Comment 4

[videoclocknet]

> 
> Do you have any suggestion on what program I could use to capture a video?  I
> would use my camera, but I wouldn't be able to keep it steady and also run the
> test.  And then again, I just only want to record a part of my screen and not
> the whole thing.


I use camstudio sometimes. It can record the screen area you select.

> 
> Also, I noticed this bug (bug 637782) "might" be also related since Google does
> use a tile system for their map that has several images in it.  So, maybe if
> that bug is fixed, this one might go away too at least somewhat (of course I
> would test after that bug is fixed to verify).  So, if bug 637782 gets fixed,
> I'll see if this is fixed too, and if it isn't, I'll do that video thing.

Hmmm, I didn't know bug 637782. It can actually be related with your current issues

Regards

Comment 5

[Wayne Mery (:wsmwk)]

(In reply to comment #3)
>  So, if bug 637782  gets fixed, I'll see if this is fixed too, and if it isn't, I'll do that video thing.

you might be waiting a while :)

Comment 6

[Nicholas Nethercote [inactive]]

Closing as incomplete due to lack of reproducibility and action.  Please reopen if this is still a problem in recent Firefox versions, such as Firefox 11.