Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Wed, 18 Feb 2004 09:13:51 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: 20040217 unhoses unzip! Message-ID: <20040218141351.GA1240@redhat.com> Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com On Tue, Feb 17, 2004 at 11:46:15PM -0500, Thomas L Roche wrote: >On Tue, 17 Feb 2004, Christopher Faylor wrote: >>> Hmm. I really don't understand why unless you were unzipping *a lot* >>> of files with long filenames. There should have been something like >>> 32MB of space to waste before you saw the problem. > >Igor Pechtchanski Tue, 17 Feb 2004 22:09:51 -0500 (EST) >> They were. 1.4G zip archives with tens of thousands of small files, >many >> with path lengths > 1k. > >That also explains why the problem only appeared well into a run (30-60 >min), and why it was unreproducible "in the small" (i.e. a testibly-bad >but sendably-short input). Even our relatively small (~100 MB) base files >unzip'ed OK throughout. > >Hoping this helps emacs, too ... can't see how, other than it's also hot >for RAM, but one can hope :-) The memory leak only happens for file names that are greater than ~130 characters or so. Unless you are doing something with A LOT of files with this characteristic in emacs, it is not likely that this is the problem. cgf -- 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/