X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Mark Geisert Subject: Re: [bash or DLL] Memory leak in childs Date: Mon, 18 Jul 2011 05:01:42 +0000 (UTC) Lines: 30 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 AZ 9901 writes: > I think I have found a memory leak in bash (or perhaps in DLL fork > implementation, I don't know). > > Just launch the following test loop having a look at Windows Task > Manager, Page File Usage tab : > > while [ 1 ] > do > test=$(echo test) > done > > Memory usage is constantly growing. > Once Cygwin closed, memory is still used, not released. Something so fundamental would have been corrected long ago if folks were seeing it in general. I don't see it on my system, for instance. It is far more likely you've got BLODA. See for details. Note that you might have BLODA that's not on that list yet because nobody's reported it as BLODA. Also note that disabling the BLODA might not make any difference; you have to remove it from your system to know for sure whether it was the problem. The above Web page gives the gory details why this is so. HTH, ..mark -- 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