FWIW, I find Acrobat Reader often hogs memory and causes swap sasms,
too. Killing FireFox and and left over acroread processes usually brings
things back.
G.
On Tue, 12 Jun 2007, Victor Churchill wrote:
> Date: Tue, 12 Jun 2007 13:06:53 +0100
> From: Victor Churchill <victorchurchill@???>
> Reply-To: Hampshire LUG Discussion List <hampshire@???>
> To: Hampshire LUG Discussion List <hampshire@???>
> Subject: Re: [Hampshire] Machine lock up and disk thrashing
>
> On 11/06/07, Vic <lug@???> wrote:
> >
> > Firefox is always the problem for me. Kill that & the machine comes back
> > to life.
>
> "me Too!!"
>
> There was a thread back in Jan '05 (thank you, GMail!) where Adrian suggested
>
> Type "about:config" into the URL bar, then adjust
> browser.cache.memory.capacity to some lower value (like 4096).
>
> http://www.mozilla.org/support/firefox/tips has some cool stuff on it BTW.
>
> Might help... but I still find that FF still grows huge and refuses to
> give the memory back until you close the very last tab (or until it
> crashes, whichever comes first...)
>
>
--
Gordon Scott http://www.gscott.co.uk
Linux ... Because I like to *get* there today.
