<?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: data segement in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/data-segement/m-p/3685310#M793900</link>
    <description>Hi nithya&lt;BR /&gt;&lt;BR /&gt;It is advisable to increase the parameter maxdsiz to temporary solve the problem.&lt;BR /&gt;&lt;BR /&gt;But it is better to analyse the process to find out what the reason of the memory leak is.</description>
    <pubDate>Tue, 06 Dec 2005 03:27:42 GMT</pubDate>
    <dc:creator>Luk Vandenbussche</dc:creator>
    <dc:date>2005-12-06T03:27:42Z</dc:date>
    <item>
      <title>data segement</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/data-segement/m-p/3685309#M793899</link>
      <description>hi all,&lt;BR /&gt;&lt;BR /&gt;i have a process which consumes memory continues  but the maxdsiz in kernal parameters is set to 64MB. so after consuming 64 MB process crashes. so in this case is it adviseable to increase the maxdsiz or there might be some problems with the process (memory leaks is ruled out as we have done the purification of the code and eliminated possible leaks)&lt;BR /&gt;&lt;BR /&gt;please advice&lt;BR /&gt;nithya</description>
      <pubDate>Tue, 06 Dec 2005 03:19:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/data-segement/m-p/3685309#M793899</guid>
      <dc:creator>nithyanandam</dc:creator>
      <dc:date>2005-12-06T03:19:06Z</dc:date>
    </item>
    <item>
      <title>Re: data segement</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/data-segement/m-p/3685310#M793900</link>
      <description>Hi nithya&lt;BR /&gt;&lt;BR /&gt;It is advisable to increase the parameter maxdsiz to temporary solve the problem.&lt;BR /&gt;&lt;BR /&gt;But it is better to analyse the process to find out what the reason of the memory leak is.</description>
      <pubDate>Tue, 06 Dec 2005 03:27:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/data-segement/m-p/3685310#M793900</guid>
      <dc:creator>Luk Vandenbussche</dc:creator>
      <dc:date>2005-12-06T03:27:42Z</dc:date>
    </item>
    <item>
      <title>Re: data segement</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/data-segement/m-p/3685311#M793901</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;A process that grows and does not shrink, even when resources should be released can be called anything you like. I'd still call it a memory leak.&lt;BR /&gt;&lt;BR /&gt;Either way, these tools might help you identify issues with your Kernel.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.hpux.ws/system.perf.sh" target="_blank"&gt;http://www.hpux.ws/system.perf.sh&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 06 Dec 2005 03:36:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/data-segement/m-p/3685311#M793901</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2005-12-06T03:36:44Z</dc:date>
    </item>
  </channel>
</rss>

