Displaying 2 results from an estimated 2 matches for "312523816inputs".
2020 Nov 25
1
[External] Re: .Internal(quit(...)): system call failed: Cannot allocate memory
...system without enough RAM, or with other
programs competing for RAM, you are likely to end up fighting with
your OS/hardware's virtual memory system. When I try to run it on a
16Gb system it churns for an hour or so before getting killed, and
/usr/bin/time reports a huge number of page faults:
312523816inputs+0outputs (24761285major+25762068minor)pagefaults 0swaps
You are probably experiencing something similar.
There may be opportunities for more tuning of the GC to better handle
running this close to memory limits, but I doubt the payoff would be
worth the effort.
Best,
luke
> It would help if...
2020 Nov 24
2
.Internal(quit(...)): system call failed: Cannot allocate memory
On 11/24/20 11:27 AM, Jan Gorecki wrote:
> Thanks Bill for checking that.
> It was my impression that warnings are raised from some internal
> system calls made when quitting R. At that point I don't have much
> control over checking the return status of those.
> Your suggestion looks good to me.
>
> Tomas, do you think this could help? could this be implemented?
I think