Oracle warns that macOS 14.4 update breaks Java on Apple CPUs


Oracle warned Apple customers to delay installing the latest macOS 14.4 Sonoma update because it will break Java on Apple silicon CPUs.

This issue frequently and intermittently causes the Jave process to terminate without warning on impacted Macs with M1, M2, and M3 processors.

It affects all Java versions, from Java 8 to the latest early access builds of JDK 22, and there are no workarounds available at the moment.

“There is no workaround available, and since there is no easy way to revert a macOS update, affected users might be unable to return to a stable configuration unless they have a complete backup of their systems prior to the OS update,” warned Aurelio Garcia-Ribeyro, Senior Director of Product Management at Oracle.

This is caused by how macOS running on Apple silicon responds when a JAVA process attempts to access memory in protected memory regions. In previous versions of macOS, the operating system would send a SIGBUS or SIGSEGV signal to the process and let it decide how to continue.

However, in macOS 14.4, the operating system now responds with a SIGKILL signal that terminates the process attempting to access protected memory. According to Garcia-Ribeyro, since the Java Virtual Machine uses dynamic code generation and accesses memory in protected memory regions to ensure correctness and performance, its process will be terminated after deploying the macOS 14.4 update.

Oracle has already alerted customers, Apple, and their OpenJDK partners and advises Apple users to delay updating until the issue is fixed.

“We recommend that users of Java on ARM-based Apple devices running macOS 14 delay applying the update until this issue is resolved,” Garcia-Ribeyro said.

More issues caused by macOS 14.4

Mac users who already installed macOS 14.4 Sonoma have also reported experiencing other problems besides Java getting killed unexpectedly, as MacRumors reported.

Other issues that users who want to update to macOS 14.4 should be aware of:

An Apple spokesperson was not immediately available for comment when contacted by BleepingComputer today.

This content is being syndicated from Source link for documentation purpose. If you are the owner of the content and like it removed, kindly contact me here and I will remove the content.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top