<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: memory leak in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-leak/m-p/3007161#M127724</link>
    <description>Hi,&lt;BR /&gt;here you can find lots of suggestions:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x77670ea029a2d711abdc0090277a778c,00.html" target="_blank"&gt;http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x77670ea029a2d711abdc0090277a778c,00.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt; Massimo&lt;BR /&gt;</description>
    <pubDate>Wed, 25 Jun 2003 13:39:51 GMT</pubDate>
    <dc:creator>Massimo Bianchi</dc:creator>
    <dc:date>2003-06-25T13:39:51Z</dc:date>
    <item>
      <title>memory leak</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-leak/m-p/3007159#M127722</link>
      <description>swap usage increase progressively.&lt;BR /&gt;I think it is cuased by memory leak.&lt;BR /&gt;How to detect which process/application has&lt;BR /&gt;memory leak?&lt;BR /&gt;&lt;BR /&gt;Tks..</description>
      <pubDate>Wed, 25 Jun 2003 13:36:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/memory-leak/m-p/3007159#M127722</guid>
      <dc:creator>Tammy Liang</dc:creator>
      <dc:date>2003-06-25T13:36:22Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-leak/m-p/3007160#M127723</link>
      <description>Hi Tammy,&lt;BR /&gt;&lt;BR /&gt;Use the command &lt;BR /&gt;&lt;BR /&gt;UNIX95= ps -e -o "vsz args" |sort -n&lt;BR /&gt;&lt;BR /&gt;(Note the space between = and ps)&lt;BR /&gt;&lt;BR /&gt;at regular intervals and note down the first column. It should not be increasing over the time. If so, that process may be having memory leak.&lt;BR /&gt;&lt;BR /&gt;-Sri</description>
      <pubDate>Wed, 25 Jun 2003 13:38:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/memory-leak/m-p/3007160#M127723</guid>
      <dc:creator>Sridhar Bhaskarla</dc:creator>
      <dc:date>2003-06-25T13:38:54Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-leak/m-p/3007161#M127724</link>
      <description>Hi,&lt;BR /&gt;here you can find lots of suggestions:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x77670ea029a2d711abdc0090277a778c,00.html" target="_blank"&gt;http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x77670ea029a2d711abdc0090277a778c,00.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt; Massimo&lt;BR /&gt;</description>
      <pubDate>Wed, 25 Jun 2003 13:39:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/memory-leak/m-p/3007161#M127724</guid>
      <dc:creator>Massimo Bianchi</dc:creator>
      <dc:date>2003-06-25T13:39:51Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-leak/m-p/3007162#M127725</link>
      <description>Hi Tammy:&lt;BR /&gt;&lt;BR /&gt;One way to detect processes with memory leaks (which are application coding errors) is to monitor a process'es virtual size over time: &lt;BR /&gt;&lt;BR /&gt;# UNIX95= ps -e -o "user,vsz,pid,ppid,args" | awk 'NR&amp;gt;1' | sort -rnk2 &lt;BR /&gt;&lt;BR /&gt;Note the blank (space) character after the equal sign and before the 'ps' command. This kimits the setting of UNIX95 to this command only. &lt;BR /&gt;&lt;BR /&gt;Note, that the virtual size (vsz) is in kilobyte size pages (see the 'ps' man pages) and excludes buffer cache and other shared components such as shared libraries and shared memory regions.&lt;BR /&gt;&lt;BR /&gt;A leaking process will grow over time. &lt;BR /&gt;&lt;BR /&gt;Remember, hoever, that if a program calls free() to free memoary it has allocated, that that memory is only freed for the program's use until such time as it terminates.  Thus seeing 100% overall memory utilization in utilities like 'glance' does not necessary signify any memory leak. &lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Wed, 25 Jun 2003 13:42:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/memory-leak/m-p/3007162#M127725</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2003-06-25T13:42:11Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-leak/m-p/3007163#M127726</link>
      <description>Hi Tammy ,&lt;BR /&gt;&lt;BR /&gt;U can use UNIX95 format command which is UNIX95= ps -eo "pid,ruser,pcpu,vsz=kbytes" -o args | sort -rn -k 4 | head&lt;BR /&gt;&lt;BR /&gt;If there is a considerable ups and downs in the memory [vsz parameter] then there should be a sure memory leak. What I suggest you to apply the patch PHSS_28618 for the OS version you have. The patch is free download from itrc.hp.com site and doesn't requier a reboot.&lt;BR /&gt;&lt;BR /&gt;shripad&lt;BR /&gt;</description>
      <pubDate>Wed, 25 Jun 2003 13:45:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/memory-leak/m-p/3007163#M127726</guid>
      <dc:creator>SSP_1</dc:creator>
      <dc:date>2003-06-25T13:45:19Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-leak/m-p/3007164#M127727</link>
      <description>In addition to above suggestions you can do following.&lt;BR /&gt;&lt;BR /&gt;1. Reboot the server &amp;amp; note down free mem (vmstat command)&lt;BR /&gt;2. Start applications &amp;amp; note down free mem&lt;BR /&gt;3. Close applications and note down free mem.&lt;BR /&gt;&lt;BR /&gt;Then you can compare the values for 1st and 3rd step. But this is bit lenghty process.&lt;BR /&gt;&lt;BR /&gt;If you have glance check following.&lt;BR /&gt;/opt/perf/examples/adviser/proc_mem_leak.&lt;BR /&gt;&lt;BR /&gt;Also as suggested use of UNIX95 variable will also give you some idea.</description>
      <pubDate>Wed, 25 Jun 2003 13:56:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/memory-leak/m-p/3007164#M127727</guid>
      <dc:creator>RAC_1</dc:creator>
      <dc:date>2003-06-25T13:56:59Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-leak/m-p/3007165#M127728</link>
      <description>Hello Tammy from Tim at B &amp;amp; W. &lt;BR /&gt;&lt;BR /&gt;This is Tim Sanko, and I can give you several hints if you are the gal I know from B&amp;amp;W I am at extension 1856. &lt;BR /&gt;&lt;BR /&gt;Tim&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 25 Jun 2003 16:40:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/memory-leak/m-p/3007165#M127728</guid>
      <dc:creator>Tim Sanko</dc:creator>
      <dc:date>2003-06-25T16:40:52Z</dc:date>
    </item>
    <item>
      <title>Re: memory leak</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-leak/m-p/3007166#M127729</link>
      <description>hi, &lt;BR /&gt;&lt;BR /&gt;if you have GlancePlus&lt;BR /&gt;&lt;BR /&gt;try &lt;BR /&gt;&lt;BR /&gt;glance -adviser_only -syntax /opt/perf/examples/adviser/proc_mem_leak&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;regards &lt;BR /&gt;&lt;BR /&gt;PMP</description>
      <pubDate>Thu, 26 Jun 2003 09:45:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/memory-leak/m-p/3007166#M127729</guid>
      <dc:creator>Patrick Preuss</dc:creator>
      <dc:date>2003-06-26T09:45:29Z</dc:date>
    </item>
  </channel>
</rss>

