X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <13019145.post@talk.nabble.com>
Date: Wed, 3 Oct 2007 06:35:46 -0700 (PDT)
From: wimxa <wimxa AT yahoo DOT com>
To: cygwin AT cygwin DOT com
Subject: RE: Huge memory leak, probably related to making new processes
In-Reply-To: <13018087.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: wimxa AT yahoo DOT com
References: <13006193 DOT post AT talk DOT nabble DOT com> <fdudpa$anu$1 AT sea DOT gmane DOT org> <13010714 DOT post AT talk DOT nabble DOT com> <loom DOT 20071003T040816-588 AT post DOT gmane DOT org> <20071003043101 DOT GA2486 AT ednor DOT casa DOT cgf DOT cx> <007a01c805aa$5f235770$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <13018087 DOT post AT talk DOT nabble DOT com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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


I have just tried this on another machine with Cygwin - no leaks. OK, so it
is not Cygwin - my bad, but I'm glad. 

Just to test, I have made a script for WIndows' cmd.exe:

@echo off
set c=1
:loop
cmd /c echo > nul
echo %c%
set /a c=%c%+1
if %c%==123456 goto end
goto loop
:end

Leaks... Not so fast as bash, but that is because executing "cmd /c" takes
much longer. It leaks approximately the same considering the numbers
represented by %c%.

So, forking in Windows itself (not Cygwin) it apparently is the whole
problem - in fact, as you mentioned - it's probably some other process (AV,
whatever) messing up with Windows' normal CreateProcessA, as bash politely
explained - and I assume the above script will also - didn't finish yet :(.

Sorry for bugging you for something that apparently is not Cygwin-related -
should have tested more.
-- 
View this message in context: http://www.nabble.com/Huge-memory-leak%2C-probably-related-to-making-new-processes-tf4557470.html#a13019145
Sent from the Cygwin Users mailing list archive at Nabble.com.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/