VSZ keeps on increasing as threads created and cancelled on rhel3.0
Sameer Suhas Deokule <[email protected]> Thu, 13 May 2004 14:17:41 -0700 (PDT)
| Newsgroups | gmane.comp.lib.phil |
|---|---|
| Message-ID | <[email protected]> |
--===============0729925797== Content-Type: multipart/alternative; boundary="0-655001285-1084483061=:65219" --0-655001285-1084483061=:65219 Content-Type: text/plain; charset=us-ascii 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. thanks Sameer --------------------------------- Do you Yahoo!? Yahoo! Movies - Buy advance tickets for 'Shrek 2' --0-655001285-1084483061=:65219 Content-Type: text/html; charset=us-ascii <DIV>Hi ,</DIV> <DIV>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.</DIV> <DIV>thanks</DIV> <DIV>Sameer</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-655001285-1084483061=:65219-- --===============0729925797== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline