[bash or DLL] Memory leak in childs
Sat Jul 23 10:41:00 GMT 2011
2011/7/21 Larry Hall (Cygwin) :
> On 7/21/2011 9:12 AM, AZ 9901 wrote:
>> 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
>> Unfortunately, it is sometime not possible to find out which component
>> is responsible, and to clean it (production environment,
>> 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.
> There have been some recent changes that could help in your situation.
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 :
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin