[plug] Tracking and Fixing Memory Leaks

[Gavin Chester]

On Sat, 2004-12-18 at 21:46, Timothy White wrote:
> Gavin Chester wrote:
> > On Sun, 2004-12-12 at 21:59, Timothy White wrote:
> >>Gavin Chester wrote:
> >>>On Sun, 2004-12-12 at 16:41, William Kenworthy wrote:

-snip-

> Sorry. I believe you may be correct. It seems to match up.
> 
> Part from my `man top`
> ---
>         o: VIRT  --  Virtual Image (kb)
>            The total amount of virtual memory used by the  task. 
>   It  			  includes
>            all  code,  data  and  shared  libraries  plus  pages that 	 
>  
>            	  have been
>            swapped out.
> 
>            VIRT = SWAP + RES.
> ---
> 
> Tim

Easy mistake - and one that's new to me.  That is, not knowing that TOP
outputs differently across different version/distros.

Back to your original topic with my variations:  You originally reported
Firefox being a memory hog.  I said I saw the same with Galeon - both
browsers built from/on the Mozilla engine.  At the time I blamed having
lots of windows and tabs open for the problem on my machine.

However, I've since seen it under different conditions.  The other day I
had just one Galeon window of five tabs open.  I let it sit there all
day (not viewing the pages) and by the end of the day Galeon alone was
gobbling up 17% of my 1Gb of memory and 90% of CPU!!!

Tim: is this anything like the memory leaks you were originally trying
to track?

Group: anyone seen anything like this and know how I can handle it??

BTW: I'm not using the latest version of Galeon (assuming the advice
would be to upgrade ;-) ), and I have a dual processor motherboard with
only one CPU fitted, so maybe it doesn't use one CPU that well? 

Regards, Gavin