Live data from Hacker News

macOS 14.4 causes JVM crashes

blogs.oracle.com

1–10 of 160 posts

Re: macOS 14.4 causes JVM crashes

#2

  An issue introduced by macOS 14.4, which causes Java process to terminate unexpectedly, is affecting all Java versions from Java 8 to the early access builds of JDK 22
If this affects so many versions of Java and nobody notices, is anyone even using Java on macOS?

Re: macOS 14.4 causes JVM crashes

#3
> "As a normal part of the just-in-time compile and execute cycle, processes running on macOS may access memory in protected memory regions."

I'm just a lowly JavaScript/TypeScript/PHP programmer, but what is the Very Good Reason that Java trying to access other processes' memory?

Re: macOS 14.4 causes JVM crashes

#4
post #2

An issue introduced by macOS 14.4, which causes Java process to terminate unexpectedly, is affecting all Java versions from Java 8 to the early access builds of JDK 22 If this affects so many versions of Java and nobody notices, is anyone even using Java on macOS?

Plenty of people develop for java on macs. The issue is that per the article this behavior was not present in the early access macOS builds, which means something changed between beta and release.

Re: macOS 14.4 causes JVM crashes

#5
post #2

An issue introduced by macOS 14.4, which causes Java process to terminate unexpectedly, is affecting all Java versions from Java 8 to the early access builds of JDK 22 If this affects so many versions of Java and nobody notices, is anyone even using Java on macOS?

For one, it doesn't affect all versions of Java. Java 20 (an LTS release) and 21, for example, don't have this problem.

Re: macOS 14.4 causes JVM crashes

#6
post #2

An issue introduced by macOS 14.4, which causes Java process to terminate unexpectedly, is affecting all Java versions from Java 8 to the early access builds of JDK 22 If this affects so many versions of Java and nobody notices, is anyone even using Java on macOS?

I'm running RubyMine on 14.3.1 all the time and it's fine. Should I hold off updating to 14.4 until the dust has settled?

Re: macOS 14.4 causes JVM crashes

#7
post #5
post #2

An issue introduced by macOS 14.4, which causes Java process to terminate unexpectedly, is affecting all Java versions from Java 8 to the early access builds of JDK 22 If this affects so many versions of Java and nobody notices, is anyone even using Java on macOS?

For one, it doesn't affect all versions of Java. Java 20 (an LTS release) and 21, for example, don't have this problem.

JDK 21 is LTS not JDK 20.

https://www.oracle.com/in/java/technologies/downloads/

Re: macOS 14.4 causes JVM crashes

#8
post #2

An issue introduced by macOS 14.4, which causes Java process to terminate unexpectedly, is affecting all Java versions from Java 8 to the early access builds of JDK 22 If this affects so many versions of Java and nobody notices, is anyone even using Java on macOS?

I'm running RubyMine on 14.3.1 all the time and it's fine. Should I hold off updating to 14.4 until the dust has settled?

You should I had some Rider and IntelliJ crashes. The crash does not happen often tough, but if your in the middle of writing code it can get you out of the flow.

Re: macOS 14.4 causes JVM crashes

#9
post #3

> "As a normal part of the just-in-time compile and execute cycle, processes running on macOS may access memory in protected memory regions." I'm just a lowly JavaScript/TypeScript/PHP programmer, but what is the Very Good Reason that Java trying to access other processes' memory?

The reasons are literally spelled out in the following paragraphs.

Re: macOS 14.4 causes JVM crashes

#10
post #2

An issue introduced by macOS 14.4, which causes Java process to terminate unexpectedly, is affecting all Java versions from Java 8 to the early access builds of JDK 22 If this affects so many versions of Java and nobody notices, is anyone even using Java on macOS?

It's not terminating directly. I've seen a few IDE crashes this week, less than one per day, but since there's no log there's no easy way to determine it's related to a macOS change.
Post reply on HN