No replies to this for about a week and we're stumped at this end - does
anyone know whether this cygwin registry key is *intended* to work or not?
Is this a bug or simply an unimplemented feature? Is it a limitation
somewhere higher up (lower down) than cygwin (in the w32 process heap
manager or something?)
Ive seen plenty of mails regarding this and this is the only solution listed
(no "it worked!" confirmation mails however). I can't see what's wrong, I'm
putting the registry key in the right place and everything, I've even logged
in as administrator and made sure the key is set in that environment too.
Has anyone allocated more than 256 megs in a cygwin compiled app?
Regards
---------------------------------
Dylan Cuthbert.
"Dylan Cuthbert" <dylan@q-games.com> wrote in message
aidgav$c23$1@main.gmane.org">news:aidgav$c23$1@main.gmane.org...
> Hi all
>
> I have edited/created the DWORD registry entry heap_chunk_in_mb (the ls of
> /proc/registry is below) and it reads 512 in regedit.
>
> I reboot but still a simple program that does new char[ 256 * 1024 * 1024 ]
> will run out of memory.
>
> AFAIK I am using the recent versions of absolutely everything. (cygcheck
> below)
>
> Any ideas what's going on, I want to run some memory intensive algorithmic
> programs and can't because of this problem.
>
> Regards
>
> ---------------------------------
Dylan Cuthbert