D'oh, I missed the "getNextEvent" part in the thread! This is Swing waiting for next events, which is normal.

What was the behaviour of the IDE on this stack trace? Why do you say that "it hangs"?

Thanks,
Antonio

El 23/3/22 a las 20:09, antonio escribió:
[2]
"AWT-EventQueue-0" #20 prio=6 os_prio=15 cpu=5912.93ms elapsed=139.99s tid=0x000000082c06c800 nid=0x36285 waiting on condition [0x00007fffddfdd000]
    java.lang.Thread.State: WAITING (parking)
     at jdk.internal.misc.Unsafe.park(java.base@11.0.14/Native Method)
    - parking to wait for  <0x00000010019c3660> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)     at java.util.concurrent.locks.LockSupport.park(java.base@11.0.14/LockSupport.java:194)     at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(java.base@11.0.14/AbstractQueuedSynchronizer.java:2081)     at java.awt.EventQueue.getNextEvent(java.desktop@11.0.14/EventQueue.java:566)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Reply via email to