How do you force Firefox to not eat all your memory?

Giles Orr gilesorr-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org
Fri Nov 14 16:19:57 UTC 2008


Hey Amanda.

I'd second the vote to look into the possibility that it's Flash
causing the problems.  I didn't like Flashblock much and have gone
with NoScript instead.  It's a pain in the ass initially as you have
to re-enable scripts on pages you use a lot that are now broken
because NoScript has shut down the entire page, but it blocks so many
lovely things (like image bugs and unnecessary JS) that I love it
despite that.  I leave the majority of Flash turned off, only turning
on the bits that I want.  With this arrangement, Iceweasel has been
almost completely stable on Debian amd64 despite running the 32-bit
Flash plugin in a wrapper (this arrangement has a very bad rep online
- and yet I've had no problems).

Please let us know what works for you - I'd like to know as I've had
problems with FF in the past.  And I doubt I'm the only one who wants
to know.  Good luck.

-- 
Giles
http://www.gilesorr.com/
gilesorr-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists





More information about the Legacy mailing list