On 4 Dec 2018, at 13:00, Gergely Buday <buday.gerg...@uni-eszterhazy.hu> wrote: > > Hi, > > https://polyml.inf.ed.ac.narkive.com/c53BJE4q/run-out-of-store-interrupting- > threads > > says that setting --maxheap with polyml can fix this problem. > > Does this memory allocation necessarily mean _physical_ memory allocation or > the operating system can use swap space to have the necessary memory?
Crudely, you can think of this as the maximum amount Poly/ML will malloc, so no, this is not physical memory allocation, this is just plain old virtual memory allocation that can be paged in/out by the operating system. James _______________________________________________ polyml mailing list polyml@inf.ed.ac.uk http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
