User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 While surfing (i.e. browsing one page after another - includes ending by about:blank) memory is not released. 110 mega-bytes an hour !!! Reproducible: Always Steps to Reproduce: 1. http://news.bbc.co.uk/ 2. http://edition.cnn.com/ 3. http://www.courrierinternational.com 4. about:blank Actual Results: Memory allocated to process increased by several mega-bytes ! Expected Results: Use little more memory than when starting. (History accounting)

Gecko (Firefox/Mozilla) reuses previously allocated memory blocks used to layout web pages and don't give them back to the OS. This, possibly combined with some small memory leaks, is what you see: memory used by gecko always increase over time. Also don't forget that java typically uses 30-50 Mb and memory cache uses 30 Mb (about:cache). I would suggest that you restart Firefox at least once per day.

(In reply to comment #1) > Gecko (Firefox/Mozilla) reuses previously allocated memory blocks used to layout > web pages and don't give them back to the OS. This, possibly combined with some > small memory leaks, is what you see: memory used by gecko always increase over > time. Also don't forget that java typically uses 30-50 Mb and memory cache uses > 30 Mb (about:cache). I would suggest that you restart Firefox at least once per day. My testing shows that Firefox on about:blank increases memory usage by about 700KB an hour on Windows XP.

Hi, I'm using firefox for about 2-3 months I've noticed the samo problem used memory always jump higher even when I close all tabs except 1 and work in it long time memory usage did not restore.

(In reply to comment #2) > (In reply to comment #1) > > Gecko (Firefox/Mozilla) reuses previously allocated memory blocks used to layout > > web pages and don't give them back to the OS. This, possibly combined with some > > small memory leaks, is what you see: memory used by gecko always increase over > > time. Also don't forget that java typically uses 30-50 Mb and memory cache uses > > 30 Mb (about:cache). I would suggest that you restart Firefox at least once > per day. > > My testing shows that Firefox on about:blank increases memory usage by about > 700KB an hour on Windows XP. > > I'll support this. I thought 'my' problem was related to java as it appeared while an online game was hanging in the background (in this occasion the 'Word Game' on KomOgVind.dk). Processor usage for this process is fairly high (30-50% while being in the background) and memory usage is constantly increased.

Mem Usage: 31'816kb VM: 20'868kb All 4 test URls + This Bug Page, + Bug list for Firefox > 1.0 Branch > Unconfirmed.

I can confirm this bug for Windows 2000, FF 1.0: leaving a ~40K page with autorefresh (via javascript "location.refresh") every 60 seconds overnight built up to ~200MB Memory Usage and ~400MB VM Size. The suggested fix from MozillaZine forums to minimize-and-restore FF frees up about half of the memory while minimized (but nothing from VM size), although this is quickly eaten up again almost in totality once the window is restored again.

I can confirm this bug !! I'm using firefox 1.0 (Linux gtk2 xft) and after 10 (ten) Minutes surfing several Pages firefox hat taken 250 MB !! (45 %) of the whole Memory !! I think that is tooo much and makes firefox unusable ..

Dupe of bug 131456.

(In reply to comment #8) > Dupe of bug 131456. Yes and NO, as this bug is not related to opening and closing TABs. This bug happens while surfing in the first and only same TAB.

(In reply to comment #9) > > This bug happens while surfing in the first and only same TAB. Right. See also bug 123191, bug 130157 and bug 174604.

*** Bug 269464 has been marked as a duplicate of this bug. ***

Not OS specific bug. Should change OS to All.

*** Bug 245746 has been marked as a duplicate of this bug. ***

I reported this bug a long, long time ago!!! I think this should be Mozilla's absolute #1 priority!!! Plz use something like MemProof or equivalent, whatever is suitable for Firefox, to solve this issue once and for all!!! There are tools out there for this kind of problems, so why not use them NOW? This is the kind of problems that will eventually make people turn back to IE etc. Plz SOLVE. Thanx.

(In reply to Fritz comment #14) > I reported this bug a long, long time ago!!! try the latest FF nightly and report back. many mozilla 1.8 fixes have been rolled into the FF nightly, so there should be improvements in memory and performance in general. failing that, your detailed data and test case would help, don't you think?

> > I reported this bug a long, long time ago!!! > try the latest FF nightly and report back. many mozilla 1.8 fixes have been > rolled into the FF nightly, so there should be improvements in memory and > performance in general. But the fact that my initial report dates from 2004-06-06 15:13 PST, which is more than 7 (seven) months ago, I guess a multitude of nightly builds have been made in the mean time. Secondly, a multitude of people have reported the same problem. Thirdly, it is perfectly clear the bug is totally reproducible; in fact, it reproduces itself all the time. What more data do you need? I repeat: there are tools available to solve memory issues. Why not use them? > failing that, your detailed data and test case would help, don't you think? No. I think using a good memory leak seeker would help. I think enough people provided enough data for you developers to solve it. Don't get me wrong: I love FF. I hate IE. But I notice I start to use IE more and more. I starts up (much) quicker and doesn't have the memory issue. FF would start up quick too if one could leave an instance running, but the mem issue makes that impossible.

(In reply to comment #16) > > > I reported this bug a long, long time ago!!! > > try the latest FF nightly and report back. many mozilla 1.8 fixes have been > > rolled into the FF nightly, so there should be improvements in memory and > > performance in general. > But the fact that my initial report dates from 2004-06-06 15:13 PST, which is > more than 7 (seven) months ago, I guess a multitude of nightly builds have been > made in the mean time. Firstly, I am not a developer. Secondly, I don't like the memory issues either, I'm just trying to provide a helpful comment to someone who is clearly frustrated. But frustration does provide useful information. In your original bug 245746 report at least one person asked you for quantitative feedback and in 7 months I don't see any- but perhaps you replied off line. Perhaps my comment about the current nightlies was not perfectly clear. FF nightlies thru January did not have many of these fixes. But in the last *2* days, hundreds of bug fixes have been integrated into FF from the mozilla base code in preparation for FF version 1.1. >Don't get me wrong: I love FF. I hate IE. Then you (and perhaps others) will want to try a RECENT nightly build.

need mlk keyword

*** Bug 286773 has been marked as a duplicate of this bug. ***

I *totally* agree with this poster. I love Firefox and have used it since v 0.6. However, the memory usage and leakage is ridiculous. The time it takes to simply CLOSE FireFox and free up those 200+ MB of Virtual Memory is on the order of 1-2. I run on a Centrino 1.3 Mhz machine, WinXP SP2, 512 MB Ram. I routinely have 7-8 other programs open in Windows at a time and can't stand the thrash from Firefox anymore. I have tried the tweaks and memory settings to no avail. I have now switched to Maxthon now that it offers most of the features of Firefox, including Gecko rendering engine support, and enhanced security features. I've tried Opera but no Onfolio support is a deal killer and I hate the ad banner up top. I miss the way bookmarks are handled in Firefox and my Slogger add-in. But I don't miss the memory hog issues. I will continue to monitor progress of the Firefox team and will switch back if this issue can be resolved. But not until then.

(In reply to comment #20) > I *totally* agree with this poster. I love Firefox and have used it since v > 0.6. However, the memory usage and leakage is ridiculous. The time it takes > to simply CLOSE FireFox and free up those 200+ MB of Virtual Memory is on the > order of 1-2. I run on a Centrino 1.3 Mhz machine, WinXP SP2, 512 MB Ram. I > routinely have 7-8 other programs open in Windows at a time and can't stand > the thrash from Firefox anymore. I have tried the tweaks and memory settings > to no avail. > > I have now switched to Maxthon now that it offers most of the features of > Firefox, including Gecko rendering engine support, and enhanced security > features. I've tried Opera but no Onfolio support is a deal killer and I hate > the ad banner up top. I miss the way bookmarks are handled in Firefox and my > Slogger add-in. But I don't miss the memory hog issues. > > I will continue to monitor progress of the Firefox team and will switch back > if this issue can be resolved. But not until then. > I love Firefox too; but for the time being I have gone back to Netscape 7.2 (another Mozilla-based free browser). When Firefox 1.1 comes out, I'll take a serious look at it; probably not before since the current nightlies break too many of my beloved extensions and themes.

After browsing with FF 1.0.1 (win2k with SP4) with multiple tabs and windows for several hours.I checked memory usage (about 170MB - causing large swap activity) I closed all but one of the windows with one tab. Still FF used 170MB of memory, then FF continued to eat more memory with every new tab.It is now beyond 200MB!!! System is largely paged to disk now (crawl).

(In reply to comment #22) > After browsing with FF 1.0.1 (win2k with SP4) with multiple tabs and windows > for several hours.I checked memory usage (about 170MB - causing large swap > activity) I closed all but one of the windows with one tab. Still FF used 170MB > of memory, then FF continued to eat more memory with every new tab.It is now > beyond 200MB!!! > System is largely paged to disk now (crawl). That's fixed by bug 131456

(In reply to comment #18) > need mlk keyword Still.

Whining about memory leaks don't help. Simple testcases will help developrs to narrow down and fix the leaks. However, given amount of leakage Firefox has, that won't be a quick fix. The ultimate help is, as always, a patch, not whining :)

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