Brent Phillips wrote:
>Hi,
>
>I've found that either there are some serious memory leaks in pTh, or I'm
>not using it properly. The most serious problem is that the stack space is
>not freed when a thread terminates. This quickly causes applications to run
>out of memory.
>
>To test this, I ran a few pth programs with a memory leak detector,
>ccmalloc (http://freshmeat.net/projects/ccmalloc). It turns up all sorts of
>memory leaks in pth- everything from the stack space to the attributes to
>the wait functions create memory leaks. (It is very simple to install and
>use.)
>
This is most likely that memory leak detector get crazy due to stack
switching via longjump (finally, pth switches this way). I used to run
tests with pth that creates tens of millions of threads and runs more
than a day, without noticeable changes in memory process consumed.
>
>Please advise! Am I missing certain clean up functions? Or are these
>serious bugs in pTh?
>
>Pretty much any pTh program that spawns a thread should exhibit this
>behavior. I can supply sample code if necessary.
>
>thanks
>
>Brent
>
>------
>
>______________________________________________________________________
>GNU Portable Threads (Pth) http://www.gnu.org/software/pth/
>User Support Mailing List [EMAIL PROTECTED]
>Automated List Manager (Majordomo) [EMAIL PROTECTED]
>
______________________________________________________________________
GNU Portable Threads (Pth) http://www.gnu.org/software/pth/
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager (Majordomo) [EMAIL PROTECTED]
