[ale] diagnosis

David Corbin dcorbin at machturtle.com
Mon Apr 19 20:05:15 EDT 2004


On Monday 19 April 2004 11:56, Geoffrey wrote:
> Dow Hurst wrote:
> > How can we find the process that is soaking the memory?  How do you
> > manipulate /proc to find out the originating process that owns the
> > memory being used?  I know IRIX had tools to look at memory and see
> > which processes owned what part of memory.  Does Linux?
> >
> > Seems if you knew what was leaking you would have a major part of the
> > battle won.
>
> I believe we mentioned top, but he noted that doesn't give him anything.
>   That's what concerns me.  If it doesn't show, is it being hidden for a
> reason???

top does show that memory is leaking, it just doesn't attirbute it to any 
process.  I know that in (ugh) Windows, you can sum up all the memory 
attributed to the applications, and come nowhere near the memory consumed 
because the OS allocates RAM for various things that are not process 
specific.  I would think that Linux might do this too.



More information about the Ale mailing list