Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Wed, 30 Jun 2004 16:11:43 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Cygwin Memory Allocation and heap_chunk_in_mb Message-ID: <20040630141143.GV19325@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Jun 30 14:54, Dan Hatton wrote: > > I'm using CYGWIN_NT-5.1, under XP Pro. > > I've set my heap_chunk_in_mb registry key to a very large value (10240 > decimal,) because I'm doing some RAM-hungry numerical calculations. > > I have enough space to do this (Control Panel->System reports 12 GB of > virtual memory allocated.) > > However, the max_memory program at > still reports > only 1.5 GB available. Sure enough, my program dies with an "out of > memory" error at 1.25 GB (the 0.25 GB discrepancy is about right for > the amount of RAM other processes are using.) > > Anyone got any ideas what's happening, please? The virtual memory available to a process is 2GB under NT. I see two possible workarounds: - There's a way to start NT with a "/3gb" switch from boot.ini which allows to get 3GB of virtual memory per process. Dunno if that's available on XP, perhaps the switch is only supported in server versions of NT. - Use the AWE (Address Windowing Extension) functions available since W2K. You have to do memory mapping by yourself as necessary. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/