[flagged]
> The issue was not present in the early access releases for macOS 14.4, so it was discovered only after Apple released the update.
There were some security fixes that were marked as under active exploitation in macOS 14.4, so my money is on those landing very steep close to the release date and this being fallout from that.
"It is also successful on the previous versions of Sonoma" (no mention of EA)
"It could not be reproduced on 23-ea+13, 22+36-2370" (EA versions of Java)
It’s possible that Java was doing something very weird, maybe undocumented/unsupported; but it’s not clear how this is anything other than Apple making a change (which I don’t see documented in their release notes) and breaking users.
Java DOES work with an EA version of Java according to the bugtrackers.
Oracle's PM doesn't know what's going on and is mixing things up.
"The issue was not present in the early access releases for macOS 14.4, so it was discovered only after Apple released the update."
JVM generates code on the fly, which normal applications are not allowed to do. So java by definition receives special treatment from the OS, which OSX seem to have broken now.
https://developer.apple.com/documentation/bundleresources/en...
https://bugs.java.com/bugdatabase/view_bug?bug_id=8327860
It says that "It is also successful on the previous versions of Sonoma", no mention of EA.
In the bug report it says it's actually not reproducable with an eary access version of Java "It could not be reproduced on 23-ea+13, 22+36-2370"
TBF I'd rather not take Oracle's Product Managment's word for granted.