X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: Date: Thu, 31 May 2012 20:16:22 +0200 Message-ID: Subject: Re: Shell script loop runs out of memory From: AZ 9901 To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id q4VIGfVb022704 2012/5/31 Jordan : > I am just wondering why the loops here are consuming increasing amounts of > memory over time?  I'm assigning new MD5 values into existing variables over and > over, not allocating new variables for each MD5 assignment. (Right??) Is 1 > second perhaps too short a delay... does the system need time to deallocate > something between each iteration of the inner loop? > You are certainly under effect of BLODA. You could have a look (there is a BLODA section in Cygwin online doc). Then, when (bash) scripting under Cygwin, you must take care to avoid forking as much as possible. You could try to improve the "sleep 1" loop with the following one : while md5sum $FILE_TO_CHECK | cut -d " " -f1 | grep -q "^$MD5PRINT$" do sleep 1 done Note that MD5PRINTNEW is no more useful here. With this loop we avoid the fork done by MD5PRINTNEW=`md5sum $FILE_TO_CHECK | cut -d " " -f1` Ben -- 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