topic Re: Tools/scripts to find out Memory Leakage in Operating System - HP-UX

Tools/scripts to find out Memory Leakage

Sandip Ghosh — Fri, 22 Feb 2002 15:45:08 GMT

Hi,

We are running a K460 with HP-UX 10.20 and Oracle 8.0.5.

Through "sarcheck" it is showing that there may be some memory leakage in some programs.

Do you know is there any tools/scripts to find out the memory leakage?

thanks in advance.
Sandip

Re: Tools/scripts to find out Memory Leakage

harry d brown jr — Fri, 22 Feb 2002 15:46:43 GMT

Glance/measureware

live free or die
harry

Re: Tools/scripts to find out Memory Leakage

Bill McNAMARA_1 — Fri, 22 Feb 2002 15:49:27 GMT

there is an internal tool called vmtrace that could help, but patching your system to the latest and greatest would be a first step.

Later,
Bill

Re: Tools/scripts to find out Memory Leakage

S.K. Chan — Fri, 22 Feb 2002 15:50:14 GMT

See attached doc .. it may help ..

Re: Tools/scripts to find out Memory Leakage

Christopher Caldwell — Fri, 22 Feb 2002 15:54:28 GMT

For pay,
look at Purify and Insure++
Buyer beware, things can get tricky when your either
testing an .sl that loaded with something like Oracle Application Server
or
your using code (executable or .sl) that depends on someone else's code (e.g. Oracle) and the leak is in someone elses code.

Both of these tools require you to be able to instrument your code (i.e. compile and link against special libraries).

Re: Tools/scripts to find out Memory Leakage

Sandip Ghosh — Fri, 22 Feb 2002 16:14:13 GMT

Bill,

I could not find vmtrace in my system. Can you please let me know from where I can get this?

Sandip

Re: Tools/scripts to find out Memory Leakage

Bill Hassell — Sat, 23 Feb 2002 00:33:31 GMT

If you are reasonably up to date on patches (full patch set less than a year old), there won't be any memory leaks from the opsystem and basic commands (except the notorious mib2agt, for which there is a patch).

So you need to track down the programs that are growing in size. There's nothing magic, just a lot of record keeping. Start by sorting all your processes by memory size:

# UNIX95= ps -eo "vsz,pid,ruser,args" | sort -rn

Then have cron run this command line every 5-10 minutes, directed into a file and look for trends as the sizes get larger. NOTE: The application may have been designed to work in that manner so verify with the authors that this is expected behavior.