X-Spam-Check-By: sourceware.org Date: Wed, 18 Jan 2006 16:59:04 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Intermittent cygwin heap allocation problem Message-ID: <20060118155904.GA16164@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <1137599559.410.252150621@webmail.messagingengine.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1137599559.410.252150621@webmail.messagingengine.com> User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 On Jan 18 10:52, Brett Serkez wrote: > [snip] > > > I also find the sleep(2000) in heap.cc when the mapping error is > > > detected rather suspicious - is this to avoid a race condition with > > > the parent? > > > > Dunno, suspect it may have been something experimental. Take a look > > at when it arrived in the CVS and check the associated changelog > > entry. > > Humm.... I wonder if this is contributing the slowness I've been seeing > during process creation.... In your opinion, is this code (sleep) > likely to be hit often? By any chance, how do you know how sleep is > implemented, does it use the OS to be awakened, or does it loop? It's Sleep, not sleep. Sleep is the Win32 version which takes a ms argument. I'm not sure why it is where it is (I assume for debugging purposes), but it doesn't hurt *at all*. When it's hit, the next step is to call api_fatal, which aborts the application anyway. 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/