Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Wed, 11 Jul 2001 13:08:21 +0200 From: Corinna Vinschen To: "'cygwin AT cygwin DOT com'" Subject: Re: heap error Message-ID: <20010711130821.J8578@cygbert.vinschen.de> Mail-Followup-To: "'cygwin AT cygwin DOT com'" References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bolten@IWE.RWTH-Aachen.de on Wed, Jul 11, 2001 at 11:26:59AM +0200 On Wed, Jul 11, 2001 at 11:26:59AM +0200, Bolten, Dierk wrote: > In this case the server program dies after 2 hours or something with : > > couldn't commit memory for cygwin heap, Win 32 error 487 Each Cygwin app gets a special heap area to hold stuff which is inherited to child processes. Eg. all file descriptor structures are stored in that heap area (called the "cygheap"). The cygheap has room for at least 4000 file descriptor structures. But - that's the clue - it's fixed size. The cygheap can't grow. It's size is reserved at the application's start and it's blocks are commited on demand. For some reason your server application needs all the cygheap space when running under the described conditions. Just a guess: Does your server forget to close file descriptors? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/