Why macOS 14.4 Crashes Java Apps: Unexpected SIGKILL on Protected Memory

SOS

macOS 14.4 introduces a problem that causes Java processes to terminate unexpectedly, crashing the application.

Affected scope:

macOS version: 14.4

Devices: Apple Silicon M1, M2, M3

Java versions: Java 8 through Java 22 (all versions)

Problem description:

In the latest macOS 14.4 update Apple added a major change that impacts applications relying on dynamic code generation and execution, such as the Java Virtual Machine (JVM). Previously, when a process accessed protected memory (a normal step in dynamic code generation), the kernel sent SIGBUS or SIGSEGV, which the process could catch and handle. In macOS 14.4, if a thread is in write mode and tries to access protected memory, the kernel sends SIGKILL, terminating the process without the chance to catch the signal.

JVMs and other technologies that depend on dynamic code generation typically use protected‑memory accesses and signal handling for correctness checks and performance optimizations. Under macOS 14.4 these applications cannot run and must wait for a fix.

macOS provides no easy rollback mechanism, so affected users cannot revert to a stable configuration unless they have a full system backup. The issue exists only in the official macOS 14.4 release; earlier preview builds did not exhibit the problem.

The change aims to strengthen memory protection on Apple‑silicon Macs, but it unintentionally breaks certain applications. Developers should monitor updates and adapt their software accordingly.