Posted on 01/24/2005 3:04:40 PM PST by Terpfen
I'm gonna give a shot. The virtual memory size has been hanging out at about 120MB. I set my memory limit to 24576, and will check see if the paged memory goes up.
I thought it was base 10 binary. (Of course, any base is base 10)
Why do geeks confuse Christmas and Halloween?
A: Because 31 OCT = 25 DEC
There is only browser.cache.memory.enable in my Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
I.e. no browser.cache.memory.capacity. Could someone advice?
You have to create the value yourself. Read the step again--it's an instruction as to how to create that value.
Oops, sorry
Not sure. Some people have the same problem. Maybe it's more of a "memory recommendation" than an actual limiter, which would make sense, especially if you have a lot of windows/tabs open constantly.
Word is Mozilla might have a fix ready for Firefox 1.1's release in June, but that's not set in stone.
I created the new entry, did a reboot and FF is still using over 27 Meg...same as before the reboot. I think I'll play with some smaller integers and see what happens.
Yes, the memory leak is still there. At the time of my posting this, these steps DID help to minimize and partially eliminate the memory leak. Changes to 1.5 make them less effective.
The best solution right now is to use config.trim_on_minimize.
Another useful tweak is to change the browser.sessionhistory.max total viewers value from -1 to 0. It disables caching of previous pages, which slows down backspacing slightly with broadband but I've noticed quite a bit less memory being used.
Also I keep config.trim_on_minimize set to false but I do have browser.cache.memory.enable on false as well. That seems to have helped somewhat.
It could be related to the extensions. Have you tried running it in safe mode for a while to see what kind of memory use you get?
I read someone's answer and tried it, the thing with the memory setting and the binary discussion. Well, it's true, it didn't work.
So, I decided, "Instead of being a lazy ass and looking for answers elsewhere, I'll simply go into the about:config and looked for myself."
Guess what? I got it right on the first shot out...
Here you go, THIS is what you need to change, VERY SIMPLE!
Find this line using the about:config in the URL = browser.cache.memory.enable
Click or double click on it so it reads: FALSE It should turn Bold also, to note the change.
I tried it, loaded up on as many pages as I could find and WHAMMO! Memory never exceeded my limits and dropped down to the 22k evertime a page would finally complete loading!!!
I now have about 10-20 forums to post this too because other people are still screaming about it.
Enjoy!
Is this issue still unsolved.. i am seeing mozilla still leaks!!
This caused some odd behaviour when I tried it on my 1.5.0.4 install. The home botton and various links in my bookmarks toolbar ceased to work, although there did seem to be an improvement. Don't know if anybody else had the same issue.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.