Re: VSZ keeps on increasing as threads created and cancelled on rhel3.0
Sameer Suhas Deokule <[email protected]> Thu, 13 May 2004 15:02:56 -0700 (PDT)
| Newsgroups | gmane.comp.lib.phil |
|---|---|
| Message-ID | <[email protected]> |
--===============1578904319== Content-Type: multipart/alternative; boundary="0-289209765-1084485776=:72674" --0-289209765-1084485776=:72674 Content-Type: text/plain; charset=us-ascii I am observing this with RHEL3.0. Any information about a patch/update that fixes this for RHEL3.0 would be appreciated.. Linux 2.4.21-4.ELsmp #1 SMP Fri Oct 3 17:52:56 EDT 2003 i686 i686 i386 GNU/Linux libpthread-0.60 libgcc_s-3.2.3-20030829 libc-2.3.2 thanks Sameer Måns_Rullgård <[email protected]> wrote:Sameer Suhas Deokule writes: > Hi , We are observing that even though number of threads in the > application is the same (rhel3.0) as the application has to create > some threads and cancel them, eventually over a period of time the VSZ > for the app. process increases. Why does the stack for the cleanly > cancelled thread not get reused when a new thread is created ? I would > expect that if the number of threads in use by the application is > constant then thread creation and cancellation should not result in > VSZ increasing over a period of time. Memory leak testing does not > indicate any leaks. I used to see something similar on my machine running regular 2.6 kernels and glibc from cvs. It stopped some time ago though. Supposedly some bug has been fixed. -- Måns Rullgård [email protected] --------------------------------- Do you Yahoo!? Yahoo! Movies - Buy advance tickets for 'Shrek 2' --0-289209765-1084485776=:72674 Content-Type: text/html; charset=us-ascii <DIV> <DIV>I am observing this with RHEL3.0. Any information about a patch/update</DIV> <DIV>that fixes this for RHEL3.0 would be appreciated..</DIV><BR> <DIV>Linux 2.4.21-4.ELsmp #1 SMP Fri Oct 3 17:52:56 EDT 2003 i686 i686 i386 GNU/Linux</DIV><BR> <DIV>libpthread-0.60</DIV><BR> <DIV>libgcc_s-3.2.3-20030829</DIV><BR> <DIV>libc-2.3.2</DIV><BR> <DIV>thanks</DIV>Sameer <BR><BR><B><I>Måns_Rullgård <[email protected]></I></B> wrote: <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Sameer Suhas Deokule <[email protected]>writes:<BR><BR>> Hi , We are observing that even though number of threads in the<BR>> application is the same (rhel3.0) as the application has to create<BR>> some threads and cancel them, eventually over a period of time the VSZ<BR>> for the app. process increases. Why does the stack for the cleanly<BR>> cancelled thread not get reused when a new thread is created ? I would<BR>> expect that if the number of threads in use by the application is<BR>> constant then thread creation and cancellation should not result in<BR>> VSZ increasing over a period of time. Memory leak testing does not<BR>> indicate any leaks.<BR><BR>I used to see something similar on my machine running regular 2.6<BR>kernels and glibc from cvs. It stopped some time ago though.<BR>Supposedly some bug has been fixed.<BR><BR>-- <BR>Måns Rullgård<BR>[email protected]</BLOCKQUOTE></DIV><p> <hr size=1><font face=arial size=-1>Do you Yahoo!?<br>Yahoo! Movies - <a href="http://movies.yahoo.com/showtimes/movie?mid=1808405861">Buy advance tickets for 'Shrek 2' </a> --0-289209765-1084485776=:72674-- --===============1578904319== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline