X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Mark Geisert <mark AT maxrnd DOT com>
Subject:  Re: Memory leakage?
Date: Sun, 10 Jun 2007 22:16:41 +0000 (UTC)
Lines: 41
Message-ID:  <loom.20070611T000610-690@post.gmane.org>
References:  <20070610115635 DOT M17897 AT edgar-matzinger DOT nl> <011901c7aba8$d2d490f0$2e08a8c0 AT CAM DOT ARTIMI DOT COM>
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: <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

Dave Korn writes:
> 
> On 10 June 2007 13:00, Edgar Matzinger wrote:
> 
> >   I wonder if there is a memory leakage problem with the current cygwin
> > release. After upgrading to it, and trying to compile Gnome (using
> > garnome), the memory usage keeps increasing. Even after I've stopped
> > the building process, the memory isn't freed up. 
> 
>   How exactly are you measuring the memory usage of a process that no longer
> exists, then?
> 
>     cheers,
>       DaveK

In my case I see it with Windows Task Manager, the PF Usage displays.  Memory 
usage slowly increases over time, seemingly when there is lots of process 
creation going on such as during large makes.  On my systems with paging turned 
off, eventually all memory is consumed and things really go to hell.

I've found an easy testcase.  Remember this bash script?
#! /bin/bash
mypath=$(pwd)
while [[ ! -z $mypath ]]
do
  mypath=$(pwd)
  if [[ -z $mypath ]]
  then
    echo "Test failed.. Path is empty."
  fi
done

I run this for a while and see gradually increasing memory usage.  Even when 
all Cygwin processes are subsequently exited, that memory is not released.  I 
also recoded that script for ash and ksh and the same thing happens, so it's 
not bash's problem.

..mark





--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/