X-Spam-Check-By: sourceware.org Message-ID: <17393e3e0612070633u457f5e9ejf7c731915231be4c@mail.gmail.com> Date: Thu, 7 Dec 2006 09:33:15 -0500 From: "Matt Wozniski" To: cygwin AT cygwin DOT com Subject: Re: 1.5.21-1 Release: Windows memory resources do not recover. In-Reply-To: <457818C5.2040708@byu.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20061277820 DOT 556531 AT privateconcern> <457818C5 DOT 2040708 AT byu DOT net> 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 Note-from-DJ: This may be spam >> I've constructed the following bash shell script (exhaustMem.bsh): > Are you SURE you don't have a buggy driver installed? Known culprits > include Agnitum outpust, Mcafee virus scanners, Logitech webcam, ... In > other words, the leak is not caused by cygwin, but by your buggy driver > leaking memory for every process spawned by your process-intensive scripts. I can't reproduce your problem either. Try running that same script in safe mode without networking, and you're pretty likely to get different results. That should prove that it's a faulty driver. ~Matt -- 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/