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 Message-Id: <5.1.0.14.2.20020924192949.0302a7e8@pop3.cris.com> X-Sender: rrschulz AT pop3 DOT cris DOT com Date: Tue, 24 Sep 2002 19:33:03 -0700 To: cygwin AT cygwin DOT com From: Randall R Schulz Subject: Re: limit for # of items created with "new" ? In-Reply-To: <20020925021050.GA10139@redhat.com> References: <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020924185910 DOT 02c3d7c8 AT pop3 DOT cris DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020924185910 DOT 02c3d7c8 AT pop3 DOT cris DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed At 19:10 2002-09-24, you wrote: >On Tue, Sep 24, 2002 at 07:06:22PM -0700, Randall R Schulz wrote: > >Hans, > > > > ... > > > >If I understand correctly, all Cygwin app memory comes out of a single pool > >(hence the Cygwin heap size registry entry), so a proper accounting of > >available memory must take the other concurrently executing Cygwin > >applications into account. > > >Sorry. This isn't correct. Each application gets its own fixed-size heap. >The heap isn't shared between applications. > >cgf Chris, No. I'm the one who's sorry for posting disinformation. Randall Schulz Mountain View, CA USA -- 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/