I haven't been able to reproduce this but I don't have a machine with
that much memory. I suspect that what is happening is that poly is
trying to allocate as much memory as possible for its own heap and not
leaving anything spare for the C++ heap. This is something I'm planning
to address
On Thu, 2010-09-16 at 12:02 +0100, David Matthews wrote:
[...] in the meantime have you tried setting the heap size with the -H
option? Try setting it to half the size of the virtual memory.
That allows poly to start up normally. -H values well above half the
size of the virtual memory also
