Why Oracle Urges Java Developers to Skip macOS Sonoma 14.4 Update

Oracle recently warned developers not to upgrade Apple Silicon macOS Sonoma to 14.4 because JetBrains IDEs are severely affected.

Apple has faced criticism for the Sonoma 14.4 update, which alters system behavior and breaks certain Java application features.

Oracle cautions Java developers not to update immediately, noting that developers using JetBrains IDEs built on the JVM have already been impacted.

The main issue is that on Apple Silicon, the OS change terminates applications without warning; only apps that rely on the previous behavior crash, not all Java programs.

Oracle Product Management Senior Director Aurelio Garcia‑Ribeyro said there is currently no workaround, and because reverting to an older macOS version is not straightforward, affected users cannot return to a stable configuration without a full backup before the OS update.

Technically, when a process accesses protected memory, earlier macOS versions (including preview builds of 14.4) sent SIGBUS or SIGSEGV signals that the OS could handle. In the released macOS 14.4, the OS sends a SIGKILL signal, causing the process to terminate immediately.

Garcia‑Ribeyro observed that the problem does not exist in the macOS 14.4 beta, meaning it was discovered only after Apple released the update. Oracle has informed Apple and OpenJDK partners, recommending Java users on ARM‑based Apple devices running macOS 14 to postpone updates until the issue is resolved.

The related OpenJDK bug is marked “unresolved” and affects JDK 8, 11, 17, 21, and 22.

JetBrains’ Maxim Kartashev stated that the issue appeared with the release of macOS 14.4; it was not present in their regular testing of the 14.4 beta, and multiple companies are researching a robust solution, which will take time.

Developers reported that JetBrains provides a pre‑release runtime that mitigates but does not fully solve the problem, and crashes still occur with the updated runtime.

One developer expressed disbelief that Apple made such a last‑minute change affecting the entire Java community without warning.

It remains unclear whether this is a macOS 14.4 bug or a deliberate security enhancement by Apple, but making such a significant change without warning is questionable.

Oracle has demanded a clear explanation from Apple.

The story serves as a reminder to enterprise teams, especially Windows administrators, about the dilemma of updating operating systems early for security patches versus delaying updates until potential damage is tested.

In short, the new OS looks good but may have pitfalls; Java developers should take special notice.