This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Created attachment 157433 [details] Threaddump containing deadlock Hi, netbeans deadlocks if it is used behind a proxy server which requires authentication. This happens e.g. at startup while the autoupdate feature tries to connect and the proxy server asks for authentication. The network stack tries to show a dialog while holding the SystemClassLoader lock. The EventQueue now blocks on SystemClassLoader.getResourcesImpl handling the "show dialog request".
There is a workaround, although it's horrible & incomplete: Disconnect the workstation from the network whilst starting the IDE. Once it has started up, plug the network back in, and immediately *change* the proxy settings via Tools/Options. It's incomplete because this doesn't stop the IDE from locking up again some time in the future... save your source code changes early and often.
Strange thing that Netbeans freeze on Autoupdate, but when I test proxy or use Check for Updates it works. And then it freezes again during loading Angular docs and so again. For me Netbeans is now useless, I can start it without network, but during work I need connection.
Same thing happened to me after an upgrade to 8.2. The previous version was running on JDK7 and didn't have this problem. I used CNTLM as a workaround. This way I don't need to set proxy authentication through Netbeans. This issue is particularly annoying because it takes a lot of time to find a root cause. Without threaddump there is no way to tell that problem has something to do with proxy settings. Netbeans just fails randomly.
This seems to be the same bug as 248308 and 262883, unfixed since 2014. Only workaround seems to be to use a local proxy. The cause of the bug is a bug in Java, which doesn't seem to get fixed unfortunately. (see 248308)
This has recurred for me with NB v8.2 and Java 1.8.152. I think it was the Java version update which re-introduced the problem... I have been using NB 8.2 for some time. However, neither of my workarounds seemed to work. :( Following from Tappe's comment, I disabled Java's automatic update checking. That seemed to get NB working again.
*** This bug has been marked as a duplicate of bug 248308 ***