X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=0.5 required=5.0	tests=AWL,BAYES_00,RCVD_NUMERIC_HELO,RP_MATCHES_RCVD,SPF_HELO_PASS
X-Spam-Check-By: sourceware.org
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: Wed, 20 Jul 2011 04:54:57 +0000 (UTC)
Lines: 32
Message-ID: <loom.20110720T064133-605@post.gmane.org>
References: <loom DOT 20110718T073757-2 AT post DOT gmane DOT org> <loom DOT 20110718T083650-815 AT post DOT gmane DOT org> <loom DOT 20110719T064243-907 AT post DOT gmane DOT org> <loom DOT 20110719T092021-102 AT post DOT gmane DOT org> <loom DOT 20110719T101702-272 AT post DOT gmane DOT org> <loom DOT 20110720T032257-444 AT post DOT gmane DOT org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
User-Agent: Loom/3.14 (http://gmane.org/)
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Mark Geisert writes:

> > int main(int argc, char** argv[])
> 
> (I won't point out the error in the above line.)
Oops ... 

> The good news is that I was then able to reproduce the issue without Cygwin.
OK - I was able to reproduce the issue too

 
> After 15 minutes, peak memory usage had gone from 227MB to 334MB and the
> system went haywire in the same fashion as before.  I rebooted again.
I start the batches with the following command (without /b):
   start test2.bat
about 10 times.
And after 7 minutes all batches are stopped with the following error:
"Für diesen Befehl ist nicht genügend Speicher verfügbar." (german WIN7)
==> "not enough memory for that command"

But the memory is freed again and win7/64 SP1 works fine. (just for information
- cause your system went haywire).

OK it really seems to be win7 problem.

I'm really glad to hear that this is not a cygwin error.

But thanks a lot for figuring that out.

heiko




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