X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Thu, 2 Feb 2012 09:56:45 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: find in root (/) results in stack trace Message-ID: <20120202085645.GB25077@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20120201150054.GA29431@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) 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 Feb 1 16:54, Heiko Elger wrote: > Corinna Vinschen writes: > > > > > This looks like a problem when recursing over the /proc/registry and > > it doesn't look like a 64 bit problem. I'll have a look. > > > > I saw same problem runing find command i.e. /cygdrive/c/Programme/cygwin (root > of my cygwin installation) ad there is no /proc/registry. Indeed. I concentrated on the registry yesterday and I found a memory and a handle leak there, which were a result of find using open/fdopendir/ closedir. This skips the close call and the registry closedir code wasn't handling that at all. Given that find wastes a lot of memory when scanning ordinary disks, too, there's apparently still another memory leak somewhere. I'm going to have another look today. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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