#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!
^--- my credentials: I've done R&D work in the past on trying to boost uptime/resilience 9's on legacy #C software in competitive markets where even small/marginal magnitudes of unavail or #latency impacts biz profit significantly
I made software more resilient in the case of certain kinds of memory bugs which would otherwise kill the flawed programs in question. Though in case of one biz it was not so much a flaw as a very aggressive architecture involving #fibers & in-house custom #stacks
synlogic