This is a standard problem on Windows whenever something tries to allocate contiguous memory due to the way it fragments your exe's memory with it's own dlls. I was able to get 1.4gb with some pretty nasty hacking of an exe once by rebasing the biggest offending dlls (it wasn't Pharo but the same principles should apply). You can find them using dependency walker. Be aware it can come with side effects as some really don't want to be moved, and as such I second Sven's OS comment ;-)
From: Usman Bhatti <usman.bha...@gmail.com>
To: Any question about pharo is welcome <pharo-users@lists.pharo.org>
Sent: Monday, 8 July 2013, 12:05
Subject: [Pharo-users] More than 500MB for windows
From: Usman Bhatti <usman.bha...@gmail.com>
To: Any question about pharo is welcome <pharo-users@lists.pharo.org>
Sent: Monday, 8 July 2013, 12:05
Subject: [Pharo-users] More than 500MB for windows
[I know there were some discussions on the topic and the topic of 64-bit VM but I'm not sure where we stand today].
I would like to know if we can allocate more than 500MB for pharo virtual machine in Windows? I am getting an "Out Of memory" msg and the following VM statistics when trying to parse a large application with Moose. Increasing the size would be the cheapest option (in terms of effort) before trying other optimizations.
tx
