401159 - Memory growth with 'new Image()' called periodically

Status: RESOLVED WORKSFORME

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

Description

[Aleksey Sanin]

We are trying to periodically update an image inside a page.  This seems to work fine, but Firefox appears to leak (or not collect) images that have been allocated with 'new Image()'.  Firefox memory usage as shown in the Windows Task Manager grows rapidly while the browser is pointing to the page with the updating image.  As soon as the browser leaves the page, the memory foot print goes down dramatically.  Is this a leak? Is there a way to force Firefox to collect earlier?

Here is an example of a page that demonstrates the issue: 

http://nenaro.com/ffimg/

Comment 1

[Aleksey Sanin]

might be a dup for #228233

Comment 2

[Robert Sayre]

That page isn't a problem on trunk. Is this a report on Firefox 2? (there is no version specified)

Comment 3

[Aleksey Sanin]

Yes, this is 2.0.0.8 

Comment 4

[Steve Chapel]

Using Firefox 3 beta 1 on Windows XP, opening the page with the demonstration caused memory usage to rise about 20 MB in 30 minutes. After that, memory usage stabilized, indicating no leak. After leaving the page, the memory cache is using 22 MB of RAM, most of which seems to be the images downloaded during the demonstration. This looks like it's not a memory problem in Firefox 3 builds, only normal caching and perhaps some fragmentation. Furthermore, Firefox 2 is getting only stability fixes, so closing as WFM.