Re: poll function don't release all windows handle / possible memory leak

2011-04-21 Thread Thomas Stalder
Works well! Many thanks. Regards, Thomas 2011/4/21 Corinna Vinschen > Thanks for the testcase.  It was another problem related to thread exit > and freeing TLS storage.  I fixed that in CVS. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/

Re: poll function don't release all windows handle / possible memory leak

2011-04-21 Thread Corinna Vinschen
On Apr 20 13:58, Thomas Stalder wrote: > Hello, > > Thanks for the fix. > > I have made some tests with the CVS version and I don't have anymore > not closed Handle, but I still have a memory leaks. Thanks for the testcase. It was another problem related to thread exit and freeing TLS storage.

Re: poll function don't release all windows handle / possible memory leak

2011-04-20 Thread Thomas Stalder
Hello, Thanks for the fix. I have made some tests with the CVS version and I don't have anymore not closed Handle, but I still have a memory leaks. I have made 2 testcases : $ gcc server.c -o server $ gcc server.c -Dnoleak -o servernoleak $ gcc client.c -o client I execute sever.exe and client

Re: poll function don't release all windows handle / possible memory leak

2011-04-18 Thread Corinna Vinschen
On Apr 18 11:35, Thomas Stalder wrote: > Hello, > > I have found that poll function don't release all windows handle (with > network socket) and generate memory leak. That's actually a pthread problem in conjunction with select (poll only calls select under the hood). I applied a fix to CVS. Th