X-Spam-Check-By: sourceware.org Date: Wed, 18 Jan 2006 18:03:44 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Intermittent cygwin heap allocation problem Message-ID: <20060118170344.GA17450@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20060118163128 DOT GC15870 AT trixie DOT casa DOT cgf DOT cx> <20060118165703 DOT GE15870 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060118165703.GE15870@trixie.casa.cgf.cx> User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 On Jan 18 11:57, Christopher Faylor wrote: > 1.5.19 may have aggravated this problem since Corinna's changes to mmap > now use VirtualAlloc'ed space for privately mmapped areas. For some > inexplicable reason, this causes more of this type of collision. I > would swear that once a program uses a memory area in a parent, windows > is much more likely to use that memory for system-like things in the > "forked/execed" child. Maybe we should use mmap from malloc only for bigger areas again. Not that I like the idea, but if it helps to lower the collisions... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/