6 ms·

It’s likely being OOM killed on Linux. Not sure what’s happening on Mac. Try allocating a terabyte of swap and it should run. Alternatively use mmap & mlock to

by _3u10 5y ago

It’s likely being OOM killed on Linux. Not sure what’s happening on Mac. Try allocating a terabyte of swap and it should run. Alternatively use mmap & mlock to verify the allocation succeeded, but the process can still be OOM killed at any time for any reason.

valleyer 5y ago
Similarly on macOS. There is a limit of 64 gigs in the VM compressor (in-core and on-disk compressed "segments" combined); when this is reached, a process that owns more than 50% of the compressed memory can be killed. See no_paging_space_action() in: https://opensource.apple.com/source/xnu/xnu-7195.81.3/bsd/kern/kern_proc.c.auto.html https://opensource.apple.com/source/xnu/xnu-7195.81.3/bsd/ke... Edit: I think the 64 gigs number is out of date -- looks like it's now based in part on the amount of physical memory in the machine.
- _3u10 5y ago
  You can tell the FreeBSD / xnu devs take their job more seriously. A failure in the VM compressor sounds so much more professional than being OOM killed.
  - saagarjha 5y ago
    This is literally just another way of saying it'll be OOM killed :/