X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Mon, 23 Nov 2009 11:01:22 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [1.7] Updated: cygwin-1.7.0-65
Message-ID: <20091123100122.GI29173@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20091119094439 DOT GC29173 AT calimero DOT vinschen DOT de>  <f4d6f44b0911191814r4653debfu24cbd4afd956f117 AT mail DOT gmail DOT com>  <20091120093210 DOT GQ29173 AT calimero DOT vinschen DOT de>  <f4d6f44b0911202003j71954bf0lf5b6696acdfe7e7d AT mail DOT gmail DOT com>  <20091121110204 DOT GB23273 AT calimero DOT vinschen DOT de>  <f4d6f44b0911210743r221b5107qfa4ebee00c9a97e9 AT mail DOT gmail DOT com>  <20091121212239 DOT GD29173 AT calimero DOT vinschen DOT de>  <f4d6f44b0911211733t15929d5ctac8e06c977bbc10c AT mail DOT gmail DOT com>  <20091123091612 DOT GE29173 AT calimero DOT vinschen DOT de>  <f4d6f44b0911230143k6437ea31n4a7788fdeef8393b AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <f4d6f44b0911230143k6437ea31n4a7788fdeef8393b@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Nov 23 17:43, Huang Bambo wrote:
> 2009/11/23 Corinna Vinschen <corinna-cygwin AT cygwin DOT com>:
> > On Nov 22 09:33, Huang Bambo wrote:
> >> And there's another quesiton:
> >> The handle of chile process( created by fork ) seems never been closed
> >> bye parent process. Is it need to be closed?
> >
> > I don't understand the question.  There's one dangling socket handle left
> > and I know where and why it happens.  Other than that, I don't see any
> > other socket handling which is left open accidentally.
> >
> While run my last test code, every time comes one connection, there
> are 3 handle leak( I monited it by Process Explorer( from
> www.sysinternals.com)), one is the chile process's handle, one is of
> "Section	\BaseNamedObjects\cygwin1S5-9770bb4ddbd85dca\cygpid.xxxx",
> the other one is of \Device\Afd.
> I mean is there any other leak with those handles.

The leak is a result of the parent process not calling wait(2) or
waitpid(2) to reap the child process.  If you let the process properly
call wait/waitpid, you won't see a leak, except for the current socket
leak this thread is about.


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