Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin-developers AT sources DOT redhat DOT com
Message-ID:	<068001c068db$b53a5780$3727f0d8@lag.net>
From:	"matt" <matt AT use DOT net>
To:	<cygwin-developers AT cygwin DOT com>
References:	<Pine DOT NEB DOT 4 DOT 10 DOT 10012032252140 DOT 25290-100000 AT cesium DOT clock DOT org> <3A2B5B4A DOT D7C85BE6 AT redhat DOT com> <20001204115202 DOT G2397 AT redhat DOT com> <20001204131445 DOT D7047 AT redhat DOT com>
Subject:	Re: bash/cygwin leaking process handles
Date:	Mon, 18 Dec 2000 02:17:21 -0800
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4522.1200

> On Mon, Dec 04, 2000 at 11:52:02AM -0500, Christopher Faylor wrote:
> >>> result: one process handle will be leaked for every repeat. There appear
> >>> to be two handles leaked just starting the original bash, though. By
> >>> handle leak, I am meaning that a process handle is still open to a
process
> >>> that no longer exists.

> Btw, it is normal to keep handles open to processes that no longer exist.
> cygwin maintains a queue of recently used process handles to avoid pid
> reuse.  The design was that some number will always be open but this
> number should not grow without bound.

You're right -- it tops off at 8 handles. I'll try and be more thorough next
time.

- Raw text -