Firefox memory Leak?

I've had issues with memory leaks too, and I found MemoryFox to be a life savor. Browser Memory Mozilla Firefox Add-on Extension – Memory Fox or https://addons.mozilla.org/en-US/fir...on/memory-fox/

I was having this annoying problem when I was using Firefox at work. After I changed some values in "about:config", memory problems never happened again. Those values are:

• javascript.options.mem.max: Its default value is -1, what I guess means automatic or unlimited. After some testing, I decided it's good to modify it to 50000, a value that appears to be in KBytes. Feel free to raise it to a proper value for you.
• javascript.options.mem.gc_frequency: Its default value is 300 (seconds?). I changed it to 5. I did not realize any overhead.

After those modifications, I started to realize that Firefox released about 5 megabytes of memory every 5 seconds and never started to take all my memory again when accessing GMail (I use it during the whole day) and other sites that like to abuse of JavaScript.

I got my coworker to change this values too and he says it worked for him. It makes me think the memory leak problem is solved!

For testing purposes people can access the "about:memory" address. the "js/gc-heap" shows how much memory the JavaScript heap is using.

I hope this is useful.

Sorry for my English. It's not my native language.

https://www.sevenforums.com/1423907-post50.html

same for me, some new tips in this thread I havent tried tho so will try them myself thanks.

well hyazndey I really got my hopes up after your post because about:memory does indeed show the memory been used by js/gc-heap. However even setting the javascript limit to 50000 and the GC to 5 seconds it still goes over it.

Why does FireFox use so much memory ? The same with Chrome it has a major memory leak. I don't like IE and with those two browsers as my only option it is really frustrating, that a browser has to page virtual memory (sometimes) Chrome is a nice browser but until they fix the memory leak issue, it falls into the same category as IE and FireFox as some great add-ons but it to as memory leak issues. When is Mozilla and Google going to finally fix these issues, they can add all the bells and whistles they want but when a browser is eating up ram that is no excuse. A browser should preform as a browser not as a power hungry app and there should be no need for extension to patch this because they are just extensions not part of the core coding of the browser.

the leak is javascript, if I disable javascript completley it doesnt happen, but of course thats not a solution as then it becomes useless as a browser.

so now I have installed noscript and testing site by site one enabled for javascript at a time, so far it seems if 'any' one site is enabled it leaks. But each site leaks at a different rate.

Given that the memory recovers on activity the bug looks to me that GC is not running when idle and waits for user activity, which to me is backwards, you would want it to run when idle and not when user activity.