X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=0.8 required=5.0 tests=AWL,BAYES_00,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:	<4E2871B5.4000101@cygwin.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> <CANs8wdA2sqpu+bW6k5narrxCvxNF7U2dpYKLQOnJQP6R9C3QFA AT mail DOT gmail DOT com> <4E2871B5 DOT 4000101 AT cygwin DOT com>
Date:	Sat, 23 Jul 2011 12:40:53 +0200
Message-ID:	<CANs8wdBGx0X77dg3VcQfd+h8F-1nk5xnyLFbwjKPJ6O46-V23g@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
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id p6NAfBQl012594

2011/7/21 Larry Hall (Cygwin) :
> On 7/21/2011 9:12 AM, AZ 9901 wrote:
>
> <snip>
>
>> 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...) ;
>> - ... ?
>
> Your best bet is to report the problem to the provider of the product
> that's interfering.  You should be able to zero in on the product by
> booting into safe mode and then turning on, one by one, the services
> that safe mode omits and running the test.  When you see the problem
> again, you'll know what product is responsible.
>
> Another alternative is to try a snapshot.
>
> <http://cygwin.com/snapshots/>
>
> There have been some recent changes that could help in your situation.
>
> --
> Larry
>

Hello,

The fact is that my scripted tools are deployed on several customers'
production environments, so it's unfortunately quite difficult (let's
say impossible) to find for each one of them the responsible product,
hoping it could be corrected.
Quite problematic situation :-/

I tested last DLL snapshot (2011-07-21), problem is still present :
http://img685.imageshack.us/img685/2394/forkq.jpg

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 -