From: Jason Duell (jcduell_at_lbl_dot_gov)
Date: Tue May 15 2007 - 15:41:19 PDT
On Tue, May 15, 2007 at 01:53:42PM -0700, Dan Bonachea wrote: > Hi Alex - > > local and global shared memory are allocated from the same area which hosts > two heaps that grow towards each other. Therefore specifying > --shared-heap=600 implies a limit where: > global heap sz on thread 0 + max local heap of any thread <= 600 > The message below indicates your program is using 578 MB of local heap and > 15 MB of global (already nearly 600 total), and then asking for at least 8 > MB more - so the limit of 600 is not enough for your program's memory > requirements. > > hope this helps.. Yes, try with '-shared-heap=1GB' or '2GB', etc (if the runtime can't allocated that much on your machine, it will just get as much as it can, and emit a warning message saying how much it actually got). -- Jason Duell Future Technologies Group <jcduell_at_lbl_dot_gov> Computational Research Division Tel: +1-510-495-2354 Lawrence Berkeley National Laboratory