X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Lewis Hyatt <lhyatt AT princeton DOT edu>
Subject:	Re: Huge memory leak, probably related to making new processes
Date:	Tue, 02 Oct 2007 17:38:52 -0400
Lines:	16
Message-ID:	<fdudpa$anu$1@sea.gmane.org>
References:	<13006193 DOT post AT talk DOT nabble DOT com>
Mime-Version:	1.0
User-Agent:	Thunderbird 2.0.0.6 (Windows/20070728)
In-Reply-To:	<13006193.post@talk.nabble.com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

wimxa wrote:
> Try executing:
> 
> find -exec echo {} \;
> 
> Simple command. This one, however, leaks at about 5kB/s. I tried the
> following:

How do you know it is leaking memory? If you are looking at Windows Task 
Manager or some similar program, then you're probably just being misled. 
The OS will automatically free the memory from each "echo" process after 
it terminates, but it may not always immediately report it as available.

-Lewis




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

- Raw text -