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 From: Matt X-Sender: matt AT cesium DOT clock DOT org To: cygwin-developers AT sources DOT redhat DOT com Subject: bash/cygwin leaking process handles Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Date: Sun, 3 Dec 2000 23:08:46 -0800 I want to say the new installer rocks and the fact that openssh/openssl is now in the default 'distribution' is great. I saw Corinna's name in the OpenSSH ChangeLog a few months ago, I figured she was up to something :) Anyways, I updated to 1.1.6 and all that good stuff on my NT4 laptop. While I was testing my update to cygcheck, I noticed the bash.exe process had some handles open to non-existant processes. (Using handleex, @ http://www.sysinternals.com/handleex.zip). You can also see this occurring by adding the Handle Count column to Task Manager. This is pretty easy to reproduce: 1. start a fresh bash instance 2. start another bash instance from inside the original instance 3. exit the last bash instance you started 4. repeat. 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. I can't tell if this happens on win9x or not since I don't have any tools that show me this kind of thing on that platform. -- it's better to burn out than to fade away