X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=1.6 required=5.0 tests=AWL,BAYES_40,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<4E26D160.8010004@valdetaro.com>
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> <4E26D160 DOT 8010004 AT valdetaro DOT com>
Date:	Thu, 21 Jul 2011 15:12:18 +0200
Message-ID:	<CANs8wdA2sqpu+bW6k5narrxCvxNF7U2dpYKLQOnJQP6R9C3QFA@mail.gmail.com>
Subject:	Re: [bash or DLL] Memory leak in childs
From:	AZ 9901 <az9901 AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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

Hello,

Thank you very much for your feedback !
I come back to the first point, memory leak when bash forks (seen in
example loops).

Following your advice and BLODA documentation, I made tests in a fresh
/ newly installed virtual environment (Windows XP / VirtualBox).
I did not notice any problem at all.
So I decided to run tests booting my suffering environment in safe
mode (F8 at boot time, then safe mode).
Once again, no problem at all.

So yes, memory leak is due to background programs which interfer with the OS.

Unfortunately, it is sometime not possible to find out which component
is responsible, and to clean it (production environment,
customers...).
So, my next question is, do you have any advice to avoid or limit memory leak ?
- specific bash scripting method / tips ;
- program to call to free memory ;
- another method to fork that would avoid memory leak (patched DLL,
wrokaround...) ;
- ... ?

Thank you very much !

Best regards,

Benjamin

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

- Raw text -