Open MidnightStallion opened 1 month ago
MidnightStallion
commented
1 month ago I have confirmed this problem also exists if you try to edit the pom.xml manually:
<dependency>
<groupId>org.slf4j</groupId>
<arti
At this point, NetBeans is completely frozen.
mbien
commented
1 month ago can you post your messages.log from next time when this happens.
instead of killing the process, can you create a thread dump and attach it? Using VisualVM is probably the easiest way to do that on windows.
MidnightStallion
commented
1 month ago There is nothing in the messages log when it happens, but here is the thread dump from VisualVM:
MidnightStallion
commented
1 month ago Actually, I take that back. After being frozen for a couple of minutes, The Add Dependency dialog automatically closed and a bunch of new stuff did get dumped into the messages log. Unfortunately, the log entries are not timestamped so I can't correlate them with when it froze up or when it finally unfroze and closed the Add Dependency dialog.
mbien
commented
1 month ago Java's event dispatch thread was still in "runnable" state when you took the thread dump:
"AWT-EventQueue-0" #35 [1636] prio=6 os_prio=0 cpu=84765.62ms elapsed=1342.86s tid=0x000001f3705f32d0 nid=1636 runnable [0x00000098bc9fc000]
java.lang.Thread.State: RUNNABLEthe warning in the log however clearly says that EDT was blocked for a long time:
WARNING [org.netbeans.core.TimableEventQueue]: too much time in AWT thread org.netbeans.modules.sampler.InternalSampler@3c5f5834So this doesn't look like the blocked UI is due to a locking issue. Was a core pinned to 100% when this happened?
You also mentioned that it was frozen "for a couple of minutes", does this mean that it worked after that again, or did you kill the process after that time?
MidnightStallion
commented
3 weeks ago Sorry for the delayed response.
Sometimes I killed it. Other times the dialog box simply disappeared after a few minutes without actually adding the dependency. The CPU was not pegged at 100%. It was around 20% or so.
Again, the same problem occurred when I tried to edit the pom.xml file by hand.
Apache NetBeans version
Apache NetBeans 22
What happened
Opened a project, right-clicked on Dependencies , then "Add Dependency". It opened the dialog to add a new Maven dependency. Clicked on GroupID and started typing. NetBeans locked up.
This is not consistently reproducible, but attempting to add maven dependencies through this dialog causes NetBeans to lock up more often than it succeeds.
Language / Project Type / NetBeans Component
Java / POM Project
How to reproduce
At this point, it will often lock up and you can do nothing except force kill NetBeans and try again.
Did this work correctly in an earlier version?
No / Don't know
Operating System
Windows 10 Professional
JDK
openjdk version 22.0.1 | OpenJDK Runtime Environment (build 22.0.1+8-16) | OpenJDK 64-Bit Server VM (build 22.0.1+8-16, mixed mode, sharing)
Apache NetBeans packaging
Apache NetBeans provided installer
Anything else
Problem occurs more than 50% of the time.
Are you willing to submit a pull request?
If it can help? Maybe. But I don't know how to do this.