In a weblog publish, Oracle’s Senior Director of Product Administration Aurelio Garcia-Ribeyro says customers of Macs with Apple Silicon processors (that’s, the M.x sequence) who depend on Java shouldn’t replace to macOS 14.4 till a present subject is resolved by Apple:
From the weblog: A difficulty launched by macOS 14.4, which causes Java course of[es] to terminate unexpectedly, is affecting all Java variations from Java 8 to the early entry builds of JDK 22. There isn’t a workaround obtainable, and since there is no such thing as a simple option to revert a macOS replace, affected customers is likely to be unable to return to a steady configuration until they’ve a whole backup of their methods previous to the OS replace.
The difficulty was not current within the early entry releases for macOS 14.4, so it was found solely after Apple launched the replace.
macOS on Apple silicon processors (M1, M2, and M3) features a function which controls how and when dynamically generated code could be both produced (written) or executed on a per-thread foundation.
As a traditional a part of the just-in-time compile and execute cycle, processes working on macOS might entry reminiscence in protected reminiscence areas. Previous to the macOS 14.4 replace, in sure circumstances, the macOS kernel would reply to those protected reminiscence accesses by sending a sign, SIGBUS or SIGSEGV, to the method. The method might then select to deal with the sign and proceed execution. With macOS 14.4, when a thread is working within the write mode, if a reminiscence entry to a protected reminiscence area is tried, macOS will ship the sign SIGKILL as an alternative. That sign can’t be dealt with by the method and the method is unconditionally terminated.
The Java Digital Machine generates code dynamically and leverages the protected reminiscence entry sign mechanism each for correctness (e.g., to deal with the truncation of reminiscence mapped recordsdata) and for efficiency. With macOS 14.4, packages that try this may now terminate as an alternative of getting the chance to deal with the sign.
Forward-of-Time compiled functions created with GraalVM Native Picture shouldn’t be affected, however your means to construct new pictures could also be.
Oracle has notified its prospects, Apple, and our companions in OpenJDK of this case. We advocate that customers of Java on ARM-based Apple units working macOS 14 delay making use of the replace till this subject is resolved.
