309686 - Firefox memory usage creeps up to around 128M when downloading many fonts from this site.

Status: RESOLVED WORKSFORME

(Toolkit :: Downloads API, defect)

Description

[Greg Eva]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

Performance gets significantly worse as the usage increases.  Closing Firefox
solves the problem temporarily.  Part of the performance problem seems to be the
"all downloads completed" message as there are many small/quick downloads going
on, it is constantly coming up, and it REALLY struggles with the animation to
hide the message.  In the meantime, you cannot do anything in Firefox for about
10 seconds until it gets a handle on things again.

Reproducible: Always

Steps to Reproduce:
1. Go to http://www.1001freefonts.com/fonts/
2. Go through the pages, and download a bunch of fonts.
3. At the bottom of each page, use the next button.
4. Tell the download manager to always save files.
5. Get through about 25 or so and you should see a problem.



Expected Results:  
The message that all downloads are completed is constantly popping up.  Even
after I would queue a couple downloads, it would finish something, and then tell
me everything was done, chug away at hiding the message, and then come up again
and tell me that everything was done again.

I would rather have control over this message popup, to be able to disable it,
or turn off the animation.

Comment 1

[José Jeria]

Please retest with Firefox 1.5 beta 1 and report back here:
http://www.mozilla.org/projects/firefox/

Comment 2

[Greg Eva]

Attachment: CPU & Memory Usage

Comment 3

[Jim Haynes]

See also 273244.  This memory leak also exists in Netscape 8.0
but doesn't appear to be in Firefox 1.5

Comment 4

[u279076]

Tested on build 2007060104 by downloading 50 fonts from the website as specified.  RAM usage for firefox is only at 56MB, nowhere near the 128MB stated.  I suggest that if Greg is still having this issue that he try upgrading his firefox to at least 2.0.0.4 as this leak seems to be fixed.