Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Date: Tue, 24 Sep 2002 22:10:50 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: limit for # of items created with "new" ? Message-ID: <20020925021050.GA10139@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <5.1.0.14.2.20020924185910.02c3d7c8@pop3.cris.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.1.0.14.2.20020924185910.02c3d7c8@pop3.cris.com> User-Agent: Mutt/1.4i On Tue, Sep 24, 2002 at 07:06:22PM -0700, Randall R Schulz wrote: >Hans, > >That looks like over 80 megabytes just for the dynamically allocated "node" >instances: > >85000 * 30 * (8 + 8) * 2 > >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 fixed-size own heap. The heap isn't shared between applications. cgf -- 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/