delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2010/03/24/12:36:23

X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Wed, 24 Mar 2010 13:36:12 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: allocate heap space shell startup failure
Message-ID: <20100324173612.GA18265@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20100324164031 DOT M12968 AT ds DOT net>
MIME-Version: 1.0
In-Reply-To: <20100324164031.M12968@ds.net>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On Wed, Mar 24, 2010 at 12:23:56PM -0500, Brian Wilson wrote:
>I have a Windows XP (SP3+updates) machine (DELL XPS, 3.2 GHz, 4Gb) running 
>McAfee AV and Smart Ram from Advanced System Care by IOBIT.com.    I've 
>attached my cygcheck output.
>
>Sometimes (about 50% of the time) when I try to start the Cygwin shell (bash), 
>by double clicking the Cygwin icon, I get an error like the attached error 
>file.  I recently updated to Cygwin 1.7.2 but was experiencing the heap space 
>allocation error in earlier versions as well.  A lot of times my installs get 
>hung trying to run the update-info.dir.sh script and I believe this error is 
>the cause (or at least related).  Even though it looks like the bash shell 
>prompt is displayed, any command I try just results in more heap space error 
>messages.

The error you're getting probably indicates that something allocated
space in a region of memory where a forked Cygwin process was expecting
to allocate the heap.  Playing with heap_chunk_in_mb won't fix this

There isn't a registry setting which will fix this.  It's likely that
either McAfee, Smart Ram, or some other resident process is interfering.
So the only way to get Cygwin running may be to stop those processes
from running entirely.

Btw, please note that the location has changed for Cygwin 1.7.2

http://cygwin.com/cygwin-ug-net/setup-maxmem.html

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019