3 ms·

FTFA: > 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 secu

by agsnu 3y ago

FTFA: > 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.

jbverschoor 3y ago
Please read the actual bugreport instead of an article written my Oracle's PM who really does not want the crap on his account.
jbverschoor 3y ago
FTBR: "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)
- agsnu 3y ago
  Right so it’s present in all shipping versions of Java back to at least 8, and the reproduction case works fine on Sonoma pre-14.4. Ergo, Apple changed something in 14.4 (a minor patch release), and it broke something in Java. I’m not sure what point you’re trying to make. 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.
  - jbverschoor 3y ago
    Yes, pre 14.4 (14.3.1 to be exact) but NOT early access of macos. The whole thread and Oracle's blogpost is about that it "suddenly broke but it was still working in a preview release of macos". 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.