On Fri, Jan 21, 2011 at 11:47 PM, Horst <knoblauch137-0...@yahoo.com> wrote:
>
>
> Firefox can be a real memory hog.
>
Haven't used Firefox much since Google Chrome for Linux came along.
But I used it for years. Maybe things have changed, but when I was
using it intensively--
-- The code was riddled with memory leaks. The longer you run it the
more memory it used, even if you had far fewer web pages open. My
work-around: Once an hour isn't too often to close the app and
relaunch it to get it back to its beginning memory consumption. If you
have trouble remembering, egg timers are very inexpensive.
-- The app loaded all installed extensions into memory unless disabled
and some of them can be memory hogs as well. My work-arounds:
1. Don't install extensions you don't really need.
2. Disable extensions you don't need very often and re-enable them
only as needed.
3. Experiment with your remaining "always on" extensions by
checking memory consumption, disabling one of them, then close the app
and relaunch, then check consumption again. Repeat an hour later. If
you identify an extension that's too greedy with your memory, look
around for another extension with equivalent functionality and test
it.
But in the end, it was Firefox's abuse of memory resources, on both
Linux and Windows, that finally sent me looking for another browser.
Now I only use it when I need to use an extension that doesn't yet
have a counterpart for Chrome.
Your mileage may vary, of course.
Best regards,
Paul
_______________________________________________
EUGLUG mailing list
euglug@euglug.org
http://www.euglug.org/mailman/listinfo/euglug
