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.
>Log Session: Friday, June 18, 2004 11:39:06 AM CEST >System Info: Product Version = NetBeans IDE Dev (Build 040617) Operating System = Linux version 2.4.20-9 running on i386 Java; VM; Vendor = 1.4.2_04; Java HotSpot(TM) Client VM 1.4.2_04-b05; Sun Microsystems Inc. Java Home = /usr/local/share/java/j2sdk1.4.2_04/jre When I edited f form class, didn't save it and then invoked Build project action (F11), the attached deadlock has been appeared. (For my next using this build I used to Save class and then invoke Build, it has worked w/o deadlocks more.)
Created attachment 15861 [details] a stack trace when the deadlock appeared
Created attachment 15863 [details] previous exception before deadlock
Editor guys, please evaluate. Is it possible, that you didn't end transaction after an exception was thrown? Anyway, please fix at least an exception and than reassign this issue back to java.
NPE fixed: /cvs/editor/src/org/netbeans/modules/editor/java/NbCompletionJavaDoc.java,v <-- NbCompletionJavaDoc.java new revision: 1.37; previous revision: 1.36 the exception appears in RP thread. MDR lock seems to be in editor.completion thread. CompletionJavaDoc is not fully rewritten using JMI model (issue #45717). It uses java source hierarchy. Also it seems there are several calls to mdr w/o transaction from CompletionJavaDoc. For now reassigning to java, feel free to reassign back...
I believe this is not a deadlock (the thread with StringBuffer.expandCapacity does not seem to be really blocked). It looks more like a long-running completion query on the background holding a transaction while AWT thread is trying to access it. AWT thread blocking is a duplicate of issue 45975 *** This issue has been marked as a duplicate of 45975 ***