X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <20070610115635.M17897@edgar-matzinger.nl> <011901c7aba8$d2d490f0$2e08a8c0@CAM.ARTIMI.COM> <20070610232043.GA7059@ednor.casa1.cgf.cx> Subject: RE: Memory leakage? Date: Mon, 11 Jun 2007 01:50:54 +0100 Message-ID: <011d01c7abc2$91528d20$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <20070610232043.GA7059@ednor.casa1.cgf.cx> Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 11 June 2007 00:21, Christopher Faylor wrote: > On Sun, Jun 10, 2007 at 10:16:41PM +0000, Mark Geisert wrote: >> Dave Korn writes: >>> >>> On 10 June 2007 13:00, Edgar Matzinger wrote: >>> >> 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. > > ...and if all Cygwin processes are subsequently exited then it isn't > Cygwin's fault either. Let's not go down this path again. Cygwin has > no magical powers to make Windows permanently use memory. Look to > resident third-party software to perform this feat, not Cygwin. Suspect your anti-virus' on-access file scanner. They've been observed to cause this kind of problem before. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/