Firefox memory usage
in
6 posts,
2 voices
Redfox
User
|
Hi, I dont know if its just me, but Ive noticed this script has a massive memory leak. I am using the latest version of FF of course, and I dont believe the config.trim_on_minimize thing even works on FF3 to reduce memory usage. I suppose this is all due to the script refreshing the sections in order for it to update, but Im not sure if its happening to just me or not. For example if I leave FF open for a few hours, I notice that it has gone up as high as 600M+ in the system resources that its using. And I know its this script, because when its disabled FF doesnt increase at all in memory usage. So anything you can do or tweak to fix this would be awesome. It personally doesnt affect me because I have a really good computer with lots of memory and RAM, but it is kind of ridiculous to have to restart FF every now and then just to dump the memory. |
urbi();
Script's Author
|
You wouldn't by any chance have Firebug enabled? That's happened to me many, many times--but only when I've had more than just the console panel on Firebug enabled; the Script and Net panels are extremely resource-intensive. Every time Firefox's memory usage has come anywhere near that high, the culprit has been Firebug. I use a fairly low-performance computer (700Mhz, 1GB Ram), and I often go to school and forget to sign-out of MySpace, and when I get back the memory usage is the same as when I left--about 100MB, give or take 20MB. |
|
Redfox
User
|
Actually yes I do have Firebug. I'll disable it and let you know how it works out. Thanks! |
|
Redfox
User
|
An update on this. I totally disabled firebug and the memory problem did show some improvement. However it is still going a bit higher than it should be, even for me. The thing for sure I noticed is this though. If your script is disabled and firebug is enabled, there is no memory leak. If its your script is enabled, and firebug is enabled also, it leaks like crazy, so definitely some weirdness going on there, but no big deal b/c I rarely used firebug anyways. I think another extension connected to this may be StumpleUpon because Im still running about 100M or so higher than normal, but Im only 90% sure at the moment so I'll keep messing with it until I figure something out. |
|
urbi();
Script's Author
|
This script makes pretty heavy use of DOM manipulation, and unfortunately, when you remove a node from the document, even though its completely inaccessible, it still remains in the browser's memory. So all the elements that are replaced when the page is updated are still in the memory for a while until the garbage collector removes them.
For me, Firefox's memory usage is at about 120MB (which is only slightly higher than usual, but I've also been using it heavily for days on end and have far more tabs than usual open) with the script and Firebug running with all panels enabled on two tabs, and with the console enabled on three others, one of which is my MySpace home page. So the script may be part of it, but I think something else is causing the majority of the extra memory consumption. |
|
Redfox
User
|
Yeah, I killed some other extensions and it seems to have stabilized around 170-220M (which is normal with my extensions etc) and not going up to 500+ like before. I have no idea which one it was though that was leaking O.o |
