[plug] Tracking and Fixing Memory Leaks

Timothy White weirdo at tigris.org
Sat Dec 18 21:46:01 WST 2004


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-
> 
> 
>>>  PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
>>> 1077 gavin     15   0 90112  70M 13380 R    67.0  7.0 348:00 galeon-bin
>>>  816 root      10   0 1179M 369M  4444 S    17.2 36.6 920:23 X
>>>    6 root       9   0     0    0     0 SW    1.5  0.0  40:53 kscand
>>>  921 gavin      9   0  8748 6044  2296 S     1.1  0.5  38:30 gkrellm
>>> 1160 gavin      9   0  6892 4876  3280 R     0.5  0.4   0:38 kdeinit
>>>32569 gavin     11   0  1116 1116   856 R     0.5  0.1   0:00 top
>>>    1 root       8   0   496  472   444 S     0.0  0.0   0:03 init
>>>    2 root       9   0     0    0     0 SW    0.0  0.0   0:00 keventd
>>>
>>>Regards, Gavin.
>>>
>>
>>Could you get the TOP output with the VIRT column? It shows the entire 
>>memory image that the proc is using.
>>
>>Thanx
>>
>>Tim
> 
> 
> I read and re-read the man page for TOP and played with different
> settings, nearly giving up to ask you tell me HOW to give what you
> wanted.  Then the penny dropped.  You may be using a different version
> of TOP than me perhaps, because the man page did not list any VIRT
> column as an option.  It appears to me that in my version of TOP, what
> you call VIRT is already given but it's headed SIZE.  There are other
> column heading differences too, such as mine saying STAT and yours S;
> mine SHARE and yours SHR; plus other examples.  So it may be that my
> original output is already giving what you want.  Happy to learn more if
> you have instructions otherwise.  

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

> 
> To help us both, I have reproduced a bit of the man page for TOP to see
> whether I am talking complete tosh, but it would be interesting to
> compare my column headings to yours.  Plus, I really am a complete
> newbie and need help learning more ;-) : 
> 
> PID  The process ID of each task.
> PPID The parent process ID each task.
> UID  The user ID of the task’s owner.
> USER The user name of the task’s owner.
> PRI  The priority of the task.
> NI   The  nice value of the task ...  
> SIZE The size of the task’s code plus data plus stack space ...
> TSIZE The code size of the task...
> DSIZE Data + Stack size. This is broken for ELF processes.
> TRS  Text resident size.
> SWAP Size of the swapped out part of the task.
> D    Size of pages marked dirty.
> LC   Last used processor.  
> RSS  The total amount of physical memory used by the task ...
> SHARE The amount of shared memory used by the task ...
> STAT The state of the task is shown here...
> WCHAN depending on the availablity ...
> TIME Total CPU time the task has used since it started...
> %CPU The task’s share of the CPU time... 
> %MEM The task’s share of the physical memory.
> COMMAND The task’s command name ...
> 
> Regards, Gavin.
> 
> _______________________________________________
> PLUG discussion list: plug at plug.linux.org.au
> http://mail.plug.linux.org.au/cgi-bin/mailman/listinfo/plug
> Committee e-mail: committee at plug.linux.org.au
> 


-- 
Tim White - Use the Fox, Luke!
PGP/GPG id: 602E944D, Pub Key Serv: subkeys.pgp.net
Fingerprint: 04C2 9682 B7B2 3006 009D  A9F3 067E EDCD 602E 944D
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me 
spread!
--
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
URL: <http://lists.plug.org.au/pipermail/plug/attachments/20041218/cf3ae0c9/attachment.pgp>


More information about the plug mailing list