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 in the next release but 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. I take it that your crashes happen immediately on start-up.
Regards, David
Tjark Weber wrote:
Running Poly/ML 5.4 on a 64-bit Linux machine with 16 GB of physical RAM, I see unexpected St9bad_alloc exceptions when I use ulimit -v with limits near 8 GB/4 GB/2 GB/1 GB. For instance,
$ uname -a Linux weber 2.6.34.6-54.fc13.x86_64 #1 SMP Sun Sep 5 17:16:27 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
$ poly -v Poly/ML 5.4 Release RTS version: X86_64-5.4.0
$ ulimit -v 8388608
$ poly terminate called after throwing an instance of 'St9bad_alloc' what(): std::bad_alloc Aborted (core dumped)
$ ulimit -v 4321280
$ poly terminate called after throwing an instance of 'St9bad_alloc' what(): std::bad_alloc Aborted (core dumped)
$ ulimit -v 2170880
$ poly terminate called after throwing an instance of 'St9bad_alloc' what(): std::bad_alloc Aborted (core dumped)
$ ulimit -v 1146880
$ poly terminate called after throwing an instance of 'St9bad_alloc' what(): std::bad_alloc Aborted (core dumped)
The same problem is present in Poly/ML 5.3. Any help would be appreciated.
Regards, Tjark
polyml mailing list polyml@inf.ed.ac.uk http://lists.inf.ed.ac.uk/mailman/listinfo/polyml