Operating System - HP-UX
1752666 Members
5460 Online
108788 Solutions
New Discussion юеВ

Tools/scripts to find out Memory Leakage

 
SOLVED
Go to solution
Sandip Ghosh
Honored Contributor

Tools/scripts to find out Memory Leakage

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
Good Luck!!!
6 REPLIES 6
harry d brown jr
Honored Contributor

Re: Tools/scripts to find out Memory Leakage

Glance/measureware

live free or die
harry
Live Free or Die
Bill McNAMARA_1
Honored Contributor

Re: Tools/scripts to find out Memory Leakage

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
It works for me (tm)
S.K. Chan
Honored Contributor

Re: Tools/scripts to find out Memory Leakage

See attached doc .. it may help ..
Christopher Caldwell
Honored Contributor

Re: Tools/scripts to find out Memory Leakage

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).
Sandip Ghosh
Honored Contributor

Re: Tools/scripts to find out Memory Leakage

Bill,

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

Sandip
Good Luck!!!
Bill Hassell
Honored Contributor
Solution

Re: Tools/scripts to find out Memory Leakage

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.



Bill Hassell, sysadmin