From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: confirm subscribe to cygwin-developers-digest@cygwin.com
Date: Fri, 19 Jul 2013 14:51:00 -0000 [thread overview]
Message-ID: <20130719125801.GB883@calimero.vinschen.de> (raw)
In-Reply-To: <20130719115741.GA4206@calimero.vinschen.de>
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.edwards@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
next prev parent reply other threads:[~2013-07-19 12:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1374159471.12713.ezmlm@cygwin.com>
2013-07-19 1:47 ` trefor.2.edwards
2013-07-19 1:56 ` Christopher Faylor
2013-07-19 11:57 ` Corinna Vinschen
2013-07-19 12:09 ` Corinna Vinschen
2013-07-19 14:51 ` Corinna Vinschen [this message]
2013-07-19 16:54 ` gcc - Is the C function select thread safe?? trefor.2.edwards
2013-07-19 22:08 ` Christopher Faylor
2013-07-22 11:26 ` Trefor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130719125801.GB883@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).