Hi Juan,
Yes I've certainly encountered similar behaviour, which is frustrating
and an ongoing delay to development.
Clearly issues were identified with Sonoma 14.4 and macOS on Apple
Silicon (https://bugs.java.com/bugdatabase/view_bug?bug_id=8327860). I
managed to bypass a significant amount of these issues by temporarily
switching to Azul Zulu OpenJDK, although it didn't resolve all issues.
Now I've updated to Sonoma 14.4.1 and have issues again, although a
little different:
Setup:
- macOS Sonoma 14.4.1
- Eclipse Temurin OpenJDK 21.0.2
- MacBook Pro M2 Max 16"
- External display (Acer Nitro XV273K)
Symptoms:
- Frequent Netbeans hangs
- usually temporary & seem to recover after a short while
following Cmd-Option-Escape to bring up Force-Quit window (note: I do
not need to actually force-quit NB in these cases)
- occasional NB sudden crash/quit
- occasional system hang & forced logout
- occasional system hang & I must force reboot
- Console/system-log fails to show any obvious pattern, although
there are a few WindowServer crashes listed for related times
- WindowServer involvement seems to make sense given increased
frequency of issues when using external display
My guess is it's some complicated interaction of new macOS WindowServer
code with Java's GUI-related code, and since Netbeans is a long-running
GUI-related process it acts as the main trigger. I seldom run other Java
GUI-based applications for long periods; if I did perhaps they'd also
trigger the issues.
Doubt it helps, but you're certainly not the only one with these issues,
and the Sonoma 14.4 update seems instrumental in introducing issues.
Stan
On 16/04/2024 10:14, Giles Winstanley wrote:
Hi Juan,
Yes I've certainly encountered similar behaviour, which is frustrating
and an ongoing delay to development.
Clearly issues were identified with Sonoma 14.4 and macOS on Apple
Silicon (https://bugs.java.com/bugdatabase/view_bug?bug_id=8327860). I
managed to bypass a significant amount of these issues by temporarily
switching to Azul Zulu OpenJDK, although it didn't resolve all issues.
Now I've updated to Sonoma 14.4.1 and have issues again, although a
little different:
Setup:
- macOS Sonoma 14.4.1
- Eclipse Temurin OpenJDK 21.0.2
- MacBook Pro M2 Max 16"
- External display (Acer Nitro XV273K)
Symptoms:
- Frequent Netbeans hangs
- usually temporary & seem to recover after a short while
following Cmd-Option-Escape to bring up Force-Quit window (note: I do
not need to actually force-quit NB in these cases)
- occasional NB sudden crash/quit
- occasional system hang & forced logout
- occasional system hang & I must force reboot
- Console/system-log fails to show any obvious pattern, although
there are a few WindowServer crashes listed for related times
- WindowServer involvement seems to make sense given increased
frequency of issues when using external display
My guess is it's some complicated interaction of new macOS
WindowServer code with Java's GUI-related code, and since Netbeans is
a long-running GUI-related process it acts as the main trigger. I
seldom run other Java GUI-based applications for long periods; if I
did perhaps they'd also trigger the issues.
Doubt it helps, but you're certainly not the only one with these
issues, and the Sonoma 14.4 update seems instrumental in introducing
issues.
Stan
On 16/04/2024 07:28, Juan Miguel Escribano wrote:
Hello there,
First, I'm not sure if the problem is in Netbeans or in Java itself
or even in macOS, but I wanted to comment it here to see if it
happens to anyone else.
My system:
MacBook Pro 16’ M2 Pro, with macOS Sonoma 14.4.1
Netbeans 21
Java: 21.0.2; OpenJDK 64-Bit Server VM 21.0.2+13-LTS
The problem only happens when I do not have the computer connected to
an external monitor. If Netbeans is on the external monitor
everything works fine, but when it is on the internal monitor is when
the problem happened to me.
What happens is that, without a defined pattern (at least I haven't
been able to find it), macOS stops responding. The mouse pointer
moves, but neither clicking nor pressing any key has any effect.
I have to press the shutdown key several times and, after a while,
the user session closes and reopens and the system responds. But if I
don't restart it then Netbeans doesn't start.
Has something like this happened to anyone?
Thank you so much
Best!
— — —
Juan Miguel Escribano
