X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=4.6 required=5.0	tests=AWL,BAYES_50,BOTNET,RCVD_IN_DNSWL_NONE
X-Spam-Check-By: sourceware.org
Message-id: <4E2871B5.4000101@cygwin.com>
Date: Thu, 21 Jul 2011 14:36:37 -0400
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-to: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: [bash or DLL] Memory leak in childs
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>
In-reply-to: <CANs8wdA2sqpu+bW6k5narrxCvxNF7U2dpYKLQOnJQP6R9C3QFA@mail.gmail.com>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
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

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

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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