|
Firefox memory leak (8)
|
Jan 11, 2006
|
I've been noticing recently that Firefox takes up several hundred MBs in the Windows Task Manager after I've opened and closed a bunch of tabs. This is a bad thing. So I looked it up.
This site says to go to "about:config", create a new integer called "browser.cache.memory.capacity", and set it equal to "16384". The problem is that this did nothing. Apparently, it only works in older versions of Firefox.
This site says to go to "about:config", create a new boolean value called "config.trim_on_minimize", and set it equal to "true". Whenever you minimize Firefox, the memory usage will go down considerably. Mozilla knows about the problem and agrees with this solution. I tried it and it worked. #technology
|
Comments:
2006-01-12 09:47:22
Definetely works. 44mb down to 2 with a minimize. Outstanding
2006-01-19 23:23:47
Thank you for this, it was just what I was looking for.
42 mb down to 1.6 when minimized, and up to only 18 when back in use for a while.
2006-01-24 18:34:18
I open a lot of tabs. 164 MB down to 6.6 MB.
2006-02-09 06:01:16
Firefox memory leak workaround
2006-02-16 12:01:40
Uh, Mozilla set that preference to its default value for a reason. If you set that to true, Windows will probably page most of Mozilla to disk when minimized. This means that when you go to restore the window, it will take forever to draw anything. You're certainly welcome to do whatever you want to your own browser, but I wouldn't recommend this for anyone. In addition, it's wrong to characterize this as a fix for a "memory leak" since paging memory to disk does not really reclaim it.
2006-02-16 13:14:43
I think I read somewhere that this "problem" isn't really a problem. It was intended to act that way for a reason. That's fine. I just know that there's a way to fix the symptom, and this frees up memory or something like that. Good enough for me.
2006-02-16 17:24:30
It probably is paging it off to disk, and I've noticed a delay of a couple seconds redrawing the window if I have about a dozen tabs open. However, I'm obviously not in great need of a lot of the information that is no longer in RAM, since it is perfectly responsive after those couple seconds, and using 50 MB less RAM. I tend to think of a memory leak as something that fills up my RAM with information I don't need (making the space unavailable to useful things), so for me, this qualifies.
2006-06-06 16:00:24
[...] As has been mentioned check out this http://ddhr.org/2006/01/11/firefox-memory-leak/ [...]
|