View in context in the libbitcoin Slack #general mirror.
In this case a kernel panic can indeed force a full system restart instead of just terminating the process. This isn't uncommon with the Darwin kernel's handling of massive shared mappings (> tens of GB), where the upfront VM address space claim (even if physical RAM/swap is available) can trigger a panic if it fragments or overflows internal limits, rather than gracefully failing with ENOMEM. Your preallocation via fallocate rules out disk-related causes, so it's almost certainly the mmap VM bug I mentioned.