To: cygwin AT cygwin DOT com
From: Heiko Elger <heiko_elger AT arburg DOT com>
Subject: Re: [bash or DLL] Memory leak in childs
Date: Mon, 18 Jul 2011 05:49:43 +0000 (UTC)
Lines: 42
Message-ID: <loom.20110718T073757-2@post.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
User-Agent: Loom/3.14 (http://gmane.org/)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

Hello,

I just can confirm the same problem with latest cygwin1.dll
(cygwin1-20110713.dll.bz2) on Windows 7/64 (fast XEON CPU).
I've seen this problem while testing other "exiter" - problem with the following
script.

*** snip snip snip ******
#!/bin/sh
set -e
while true; do
   ./exiter.exe
echo -n $?
done
*** snip snip snip ******

Please regard: exiter is a native WIN32 executable.

The virtual memory (windows task manager) grows and grows over the time.

The cygwin eats all memory til no more available.
But after alle cygwin processes are closed the memory is freed.

I did another native cygwin test using true.exe:

*** snip snip snip ******
#!/bin/sh
echo "starting $0"
while /usr/bin/true
do
    :
done
echo "exiting $0"
*** snip snip snip ******

Using this script the used virtual memory (windows task manager) grows too, but
even more slowly - so you have to run this script a long time.

Best regards

Heiko Elger


--
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