#Java crash bug on #macOS 14.4 is in my wheelhouse (resilience.)
Root cause seems to be they changed what signal the OS sends to a process when certain kind of mem access is attempted
In the case in question the kernel previously delivered a SIGBUS or #SIGSEGV
If you've ever heard of a program crashing via a so-called #segfault it means the process received a #SEGV sig, it did NOT handle it explicitly (& robustly) & the default behavior was to crash
now they SIGKILL it! *cannot* be handled!



