Hacker News Reader

Comment by xcv123 | Hacker News Reader

".. is affecting all Java versions from Java 8 to the early access builds of JDK 22. There is no workaround available .."

Do not update until Apple fixes the issue.

View on HN

Isn’t this something Oracle will be fixing? Seems like it from other comments here.

No. Oracle will not fix jre8 because it's too old. Oracle will not fix corretto jre, because it's not theirs.

They may not fix it, but my understanding is they are relying on undocumented features and that's always a crap shoot. My company does low-level language stuff and we've been burned like this, too. We decided not to trade performance for compatibility in the last decade or two.

EDIT: maybe not undocumented, but undefined behavior?

Documented in the POSIX specification. It is a kernel bug.

Is it Apple or Oracle who should rightly be fixing this issue?

It's a bug in macOS and it breaks POSIX compliance. Oracle can develop a workaround but Apple should fix it in their next update.

bug? POSIX compliance? How?

When a kernel update breaks all JVM versions starting from Java 8, the kernel devs fucked up. Even worse when the breaking change is in the final production release only and not the beta release. Completely obvious that this is a bug.

Segmentation fault should trigger SIGSEV, not SIGKILL. They changed the behaviour of the kernel which broke the JVM and any other applications that are designed according to the POSIX standards. https://pubs.opengroup.org/onlinepubs/9699919799/functions/V...

right, seems like sort of a no brainer that if a minor version bump of an OS completely breaks JDK8, that’s on the OS developer.

Reply on news.ycombinator.com