Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Mon, 4 Dec 2000 21:19:37 +0300 From: Egor Duda X-Mailer: The Bat! (v1.45) Personal Reply-To: Egor Duda Organization: DEO X-Priority: 3 (Normal) Message-ID: <74172542523.20001204211937@logos-m.ru> To: Matt CC: cygwin-developers AT sources DOT redhat DOT com Subject: Re: bash/cygwin leaking process handles In-reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Monday, 04 December, 2000 Matt matt AT use DOT net wrote: M> Anyways, I updated to 1.1.6 and all that good stuff on my NT4 laptop. M> While I was testing my update to cygcheck, I noticed the bash.exe process M> had some handles open to non-existant processes. (Using handleex, @ M> http://www.sysinternals.com/handleex.zip). You can also see this occurring M> by adding the Handle Count column to Task Manager. M> This is pretty easy to reproduce: M> 1. start a fresh bash instance M> 2. start another bash instance from inside the original instance M> 3. exit the last bash instance you started M> 4. repeat. i cannot reproduce it on my home build dated 2000-11-24. i'm using Nt 4.0 sp 5. handle count is stable, and nthandle utility from sysinternals shows no new handles owned by parent bash process no matter how much times i repeat. maybe you have something special in your ~/.bashrc or ~/.profile? i know at least one possible reason of handle leak -- ntvdm.exe opens %SystemRoot%/system32/ega.cpi each time some dos program runs in console window, but never closes them. since ntvdm is started only once per console group, we have handle leak. However, all those leaked handles go to ntvdm, not to bash, so it doesn't match your description. anyway, you may want to use nthandle from sysinternals to see, what those leaked handles really are -- files, pipes, sockets, etc. And make sure you have "clean" environment -- use standard .bashrc and .profile Btw, what about using sh instead of bash? do sh leaks handles too? Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19