On 4 Dec 2018, at 15:59,
wrote:
> On Tue, Dec 4, 2018 at 2:21 PM +0100, "David Matthews"
> wrote:
>> On 04/12/2018 13:00, Gergely Buday wrote:
>> > Hi,
>> >
>> > https://polyml.inf.ed.ac.narkive.com/c53BJE4q/run-out-of-store-interrupting-
>> > threads
>> >
>> > says that setting --maxheap wi
Thanks, David.
Digging into the issue it might be that the polyml in question uses 32 bit
addressing an that is the problem.
How can I check whether a polyml is 32 or 64 bit?
- Gergely
Az Android Outlook letöltése
On Tue, Dec 4, 2018 at 2:21 PM +0100, "David Matthews"
wrot
On 4 Dec 2018, at 13:00, Gergely Buday 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
>
On 04/12/2018 13:00, Gergely Buday 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
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