bash/cygwin leaking process handles

Christopher Faylor cgf@redhat.com
Mon Dec 4 10:14:00 GMT 2000


On Mon, Dec 04, 2000 at 11:52:02AM -0500, Christopher Faylor wrote:
>On Mon, Dec 04, 2000 at 09:52:26AM +0100, Corinna Vinschen wrote:
>>Matt 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.
>>
>>Did you check that with 1.1.4 or 1.1.5 as well? Would be interesting
>>to know if that's a new problem.
>
>And, it would be interesting to have the problem debugged, actually.
>This is "cygwin-developers", right?

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.

cgf


More information about the Cygwin-developers mailing list