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 142559 [details] Full thread dump. See http://deadlock.netbeans.org/job/NB-Core-Build/834/testReport/org.netbeans.modules.maven/ProjectOpenedHookImplTest/testGeneratedSources/ This is a deadlock: In Thread Test Watch Dog: testGeneratedSources: sun.awt.SunToolkit.initEQ(SunToolkit.java:115) is calling Class.forName("java.awt.EventQueue"); while it holds a lock from PlatformLogger.getLogger() and in Thread RequestProcessor queue manager: we're in Class.forName("java.awt.EventQueue") which calls sun.util.logging.PlatformLogger.getLogger(PlatformLogger.java:196) Since RequestProcessor access Java private classes, IMHO the source of the problems is there.
Maybe it would help if the sun.awt.AppContext code is executed in EQ?
Maybe the issue is solved in JDK 8 by http://hg.openjdk.java.net/jdk8/jdk8/jdk/rev/b3d6953b9829 ?
Deadlock in JDK is a JDK problem I think.
(In reply to Martin Entlicher from comment #2) > Maybe the issue is solved in JDK 8 by > http://hg.openjdk.java.net/jdk8/jdk8/jdk/rev/b3d6953b9829 ? Martine, are we sure that change fixes the problem for us? The change is scheduled for backport into 7u60, so I'd like to add a note there that NetBeans encourages the backport.
https://bugs.openjdk.java.net/browse/JDK-8019853
The change in JDK 8 definitely modifies the code that is involved in the deadlock and should assure that this particular deadlock will not occur any more.
The build seems to use jdk1.7.0_45. According to https://bugs.openjdk.java.net/browse/JDK-8019853 it's fixed already in more recent JDK 7 and in JDK 8. This bug should not occur after we change the NB builder to use JDK 8.