On Jul 19 13:57, Corinna Vinschen wrote: > On Jul 19 13:40, Corinna Vinschen wrote: > > On Jul 18 15:15, Christopher Faylor wrote: > > > [What an odd subject line] > > > On Thu, Jul 18, 2013 at 04:23:32PM +0100, trefor.2.edwa...@bt.com wrote: > > > >I have a very recent version of Cygwin and using the SIPP application. > > > >This calls nanosleep from within a thread. > > > > > > "Very recent" is not a precise enough distinction for debugging > > > problems. > > > > > > See: http://cygwin.com/problems.html . > > > > > > >Effectively , every second, the application > > > > > > > >* Creates a thread > > > > > > > >* Calls nanosleep 9 times. > > > > > > > >* Deletes the thread > > > > > > > >And every second, according to windows task manager, it one more handle > > > >is being used. Eventually it runs out of resources and crashes. > > > > > > Seems like a simple test case would show this. Please provide one. > > > > I think I know what's going on, but cgf is right, a simple testcase > > showing this behaviour would be helpful for testing. > > Never mind, I created my own testcase. My hunch was correct, the > per-thread timer handle didn't get closed when the thread exits. > > I applied a patch, and I'll create new Cygwin snapshots for 32 and 64 > bit today. Pleas give them a try (http://cygwin.com/snapshots/).
Snapshots are up. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
