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: Thu, 25 Nov 2004 01:15:21 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Setup and memory usage Message-ID: <20041125061521.GG3845@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <20041125060734 DOT 2014584C3C AT pessard DOT research DOT canon DOT com DOT au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041125060734.2014584C3C@pessard.research.canon.com.au> User-Agent: Mutt/1.4.1i On Thu, Nov 25, 2004 at 05:07:33PM +1100, Luke Kendall wrote: >Some weeks ago, I seconded a report that Cygwin wasn't releasing >handles, causing some machines to thrash to death and the installation >to fail. > >I can report that the problem is slightly improved in the current >release of setup, Er, there hasn't been any release of setup since the original reports. The last release was on April 25, 2004. >It would be really good if setup.log could be written incrementally. >It would make setup crashes more debuggable, and should use less >memory, too. Perhaps you might like to follow the discussions about setup in cygwin-apps then you could see just what is going on and what's being planned for future releases. 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/