MIME-Version: 1.0
In-Reply-To: <4FC7C859.5050909@cs.umass.edu>
References: <loom.20120531T193933-322@post.gmane.org>	<CANs8wdBYOBGsmp2iFSSOOd5FZ4qb3i3a-E2EM8LBbPKz=su5Pg@mail.gmail.com>	<786EBDA1AC46254B813E200779E7AD36023A42C2@srv1163ex1.flightsafety.com>	<loom.20120531T211830-607@post.gmane.org>	<4FC7C859.5050909@cs.umass.edu>
Date: Thu, 31 May 2012 22:14:59 +0200
Message-ID: <CANs8wdBdVfsMTCrosNt7TSJpccsCHRwFbQ8wmLpbFMCcLTUzHQ@mail.gmail.com>
Subject: Re: Shell script loop runs out of memory
From: AZ 9901 <az9901@gmail.com>
To: moss@cs.umass.edu, cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Transfer-Encoding: 8bit

2012/5/31 Eliot Moss <moss@cs.umass.edu>:
>> 1.  Does "fewer forks" mean that some forks are still occurring, thus the
>> same
>> memory crash will still happen, but not right away?  Just delaying the
>> inevitable, for longer than my original script does?
>
>
> I think so, assuming the problem is that forks are not getting fully
> reclaimed.

I think so too ; when I intensively script under Cygwin, I have to
reboot after some time because the machine runs out of memory.
I made some tests, forks are clearly the root cause yes, they are not
fully reclaimed.

Make an infinite loop with no fork, and look at the memory usage.
Then, make an infinite loop with one fork and look at the memory :-/

I really hope a solution will be found one day :-)

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