This is the mail archive of the
mailing list for the Cygwin project.
RE: confirm subscribe to cygwin-developers-digest at cygwin dot com
- From: <trefor dot 2 dot edwards at bt dot com>
- To: <cygwin at cygwin dot com>
- Date: Thu, 18 Jul 2013 16:23:32 +0100
- Subject: RE: confirm subscribe to cygwin-developers-digest at cygwin dot com
- References: <1374159471 dot 12713 dot ezmlm at cygwin dot com>
I have a very recent version of Cygwin and using the SIPP application. This calls nanosleep from within a thread.
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.
If I comment out the call to nanosleep, the number of handles stay steady.
If the problem was just within nanosleep, the I would expect it to "leak" 9 handles every second, but it only one is leaked. So I'm assuming that it somehow. It's a combination of the thread and the calls to nanosleep.
Hence my question, is nanosleep thread safe?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple