DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=YG0i0E9cbzq4bChIJOOdnhLCsmVU/gnOlvd0i3qWxPzAS78wCNwm5
	QvaRJ4j/11yPS/QjjhLXfgt+votTZCyRScmYhjhh5eSQGEZE5r9UDpY7Lvj1/G8a
	H135BMGx0x4HiGEswBKsQXzX/OWBcHsWGcODZWJdtlHudiW99q9WzQ=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 19 Jul 2013 14:58:01 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: confirm subscribe to cygwin-developers-digest@cygwin.com
Message-ID: <20130719125801.GB883@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <1374159471.12713.ezmlm@cygwin.com> <107C24740CC429479D55901D6AAD17E43C536ABB87@EMV61-UKRD.domain1.systemhost.net> <20130718191509.GA588@ednor.casa.cgf.cx> <20130719114047.GG20871@calimero.vinschen.de> <20130719115741.GA4206@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20130719115741.GA4206@calimero.vinschen.de>
User-Agent: Mutt/1.5.21 (2010-09-15)

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