5 ms·

Did you read Oracles post? "The issue was not present in the early access releases for macOS 14.4, so it was discovered only after Apple released the update."

Did you read Oracles post? "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.

self_awareness 3y ago
It's not that Java has a special treatment, but all applications who "request it" are allowed (for example also JavaScript engines in browsers). https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_security_cs_allow-jit https://developer.apple.com/documentation/bundleresources/en...
jbverschoor 3y ago
I did and also the bugreport. https://bugs.java.com/bugdatabase/view_bug?bug_id=8327860 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.
grodriguez100 3y ago
There is no “special treatment for Java”. This is a well known technique that has been used for ages in the implementation of JITs. The behavior it relies on is specified by POSIX.