Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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: Tue, 24 Sep 2002 23:03:15 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: limit for # of items created with "new" ?
Message-ID: <20020925030315.GB10139@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020924185910 DOT 02c3d7c8 AT pop3 DOT cris DOT com> <amqoqi$a3e$1 AT main DOT gmane DOT org> <Pine DOT GSO DOT 4 DOT 44 DOT 0209241841560 DOT 7805-100000 AT slinky DOT cs DOT nyu DOT edu> <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 20020924192949 DOT 0302a7e8 AT pop3 DOT cris DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5.1.0.14.2.20020924192949.0302a7e8@pop3.cris.com>
User-Agent: Mutt/1.4i

On Tue, Sep 24, 2002 at 07:33:03PM -0700, Randall R Schulz wrote:
>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.
>
>Chris,
>
>No. I'm the one who's sorry for posting disinformation.

Well, that's a pretty rare event, so I think you can be excused, just
this once.  :-)

I think what may be confusing in this case is that cygwin's shared
memory region is getting corrupted.  I think it's due to the fact that
something is walking off the end of the heap.  I don't know why an
exception isn't being thrown though.

FWIW, the next version of cygwin may actually be able to deal with this
scenario a little better.  It uses Doug Lea's malloc package and may be
able to allocate memory using mmap.  I haven't actually tried this
scenario yet but if anyone wants to try a recent snapshot, it might be
informative.

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/