From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: poll function don't release all windows handle / possible memory leak
Date: Thu, 21 Apr 2011 17:39:00 -0000 [thread overview]
Message-ID: <20110421081446.GG3324@calimero.vinschen.de> (raw)
In-Reply-To: <BANLkTi=mkaq2tBp-BO7MzM_Cvc05si4Dmw@mail.gmail.com>
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. I fixed that in CVS.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader 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:[~2011-04-21 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTi=GgZfG_QwAWtyqAYQeqOwEbcSFLw@mail.gmail.com>
2011-04-18 10:31 ` Thomas Stalder
2011-04-18 19:14 ` Corinna Vinschen
2011-04-20 13:22 ` Thomas Stalder
2011-04-21 17:39 ` Corinna Vinschen [this message]
2011-04-21 17:54 ` Thomas Stalder
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=20110421081446.GG3324@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).