 
| Subject: | |
| From: | |
| Reply To: | |
| Date: | Tue, 10 Mar 1998 17:06:27 -0800 |
| Content-Type: | text/plain |
| Parts/Attachments: |
|
|
Re:
> > I've been asked how you can determine if a process might have a memory leak.
...
> > If no tools exist to provide this info, I assume it could probably be obtained
> > via :DEBUG and examining the various memory pointers in the PIB and PIBX etc.
Well, I can't tell you (yet :) how much heap you've malloc'd, I can tell you:
<plug>
- how much heap you have in MEMORY at this time
- how much heap you have allocated (NMHEAPSIZE)
For an example of the former, note the "#HeapPgs" column ... that's the number
of pages (a page is 4096 bytes) of heap space in memory for the process at
this moment.
Note: this requires SHOT version 2.16 or later.
:run shot.pub.lpstools
SHOT [2.16] - LPS Toolbox [A.02b] (c) 1995 Lund Performance Solutions
For Help at the SHOT prompt enter ? My PIN is 107
For NEWS, enter: HELP NEWS
MPE/iX 5.5; System started @ 12:45 on 1998/3/1
Highest PIN in use = 118, max pin possible = 8190, highest ever used = 192
SHOT @ TUE, MAR 10, 1998, 5:02 PM
SHOT [Delta]: adm + heappages
SHOT [Delta]: all
? PIN CPU Process Name Pri Q Delta % Ic #HeapPgs Wait State
- --- ------ -------------------------- --- - ----- --- -- -------- ------------
...
22 3497 CI.PUB.SYS 152 C Nn 48 TERMINAL_READ
23 378 CI.PUB.SYS 202 D Nn 32 SON, FATHER
39 1825 LOG.PUB.SYS 50 B Nn SYSLOG
40 657 SYSMAIN.PUB.SYS 49 B Nn SYSMAIN_PORT
...
104 3127s HTTPD.OMI.WWW 216 D nn 173 MESSAGE_WAIT
107 501 SHOT.PUB.LPSTDEV 185 C 95 1 Nn 48 (executing)
109 6370 HTTPD.OMI.WWW 238 D nn 161 MESSAGE_WAIT
112 5209 VTSERVER.NET.SYS 152 C Nn 32 TERMINAL_READ
114 135463 QEDIT.PUB.ROBELLE 152 C Nn 32 TERMINAL_READ
...
# PINs: 101 (# processes since bootup: 26,195)
CPU status: busy 1%, idle 99% (113 CPU out of 7284)
# Page faults: none.
</plug>
--
Stan Sieler [log in to unmask]
http://www.allegro.com/sieler.html
|
|
|
