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.
I have just switched from build 201012010001 to 201012030001 and it keeps freezing after a short while. It is unusable. I will upload the dump later today.
we can do nothing without thread-dump, please reopen once attached.
Created attachment 103608 [details] Thread dump Thread dump uploaded.
reassign for evaluation
Seems like a duplicate of issue 191717 fixed in the build from Dec/5. Please, try a new daily build and reopen with a new thread dump (or a few of them taken with several seconds between them) if you encounter the same problem again. Thanks. *** This bug has been marked as a duplicate of bug 191717 ***
Hi, the bug you referenced says the fix would have been available from build *201012050001* but I am on that build and still have the problem.
Thanks for providing more information. Please reopen with additional thread dumps (the provided one is only one snapshot of the threads in time and may not reveal all that is happening). Also tell us what you are doing in the IDE and what you have opened (projects, files in editor,...) when the problem appears.
Created attachment 103860 [details] Dump for build 201012090001 The problem is still there in lastest build 201012090001. The IDE is unusable like this. Please help.
Setting to P1 according to http://wiki.netbeans.org/BugPriorityGuidelines, section "crash or deadlock". W/a is to use an external xml editor. There is no w/a in NetBeans itself.
Changing the report to P1 really does not help to have the problem resolved. I need what I asked above from you. 1. additional thread dumps http://wiki.netbeans.org/GenerateThreadDump 2. tell me what you are doing in the IDE when the problem appears
Created attachment 103866 [details] Stack trace tool dump I had missed your previous update, sorry. I have uploaded a trace generated with the StackTrace tool.
The stack trace I have just uploaded was generated after clicking on a struts-config.xml file. NetBenas froze and never gave back control.
Priority is set according to the NetBeans guidelines.
The last thread dump is showing a deadlock between * AWT-EventQueue-0 which acquired AWTTreeLock for the painting and now is waiting for PriorityMutex in o.n.m.e.lib2.view.DocumentView.viewToModelChecked and * Timer-4 thread which has PriorityMutex acquired in o.n.m.e.lib2.view.ViewUpdates.checkRebuild and is waiting for AWTTreeLock for paiting The use of PriorityMutex was introduced in http://hg.netbeans.org/main/rev/c9a397f44346 (btw, besides fixing the deadlock, also the painting should probably be rescheduled from the other thread to AWT) Reassigning to editor.
Created attachment 103913 [details] dump201012100001.txt STACK TRACE TOOL Issue is still there in build 201012100001 Please fix this, it is very annoying: - I have to kill the process - Restart NetBeans - Use an external editor to edit xml files
Created attachment 104001 [details] IDE Freeze just tring to open a source file I have been having issues with the nightly builds since early December, also on XP. IDE freezes very quickly and has to be terminated with the task manager. Often a simple cut of a single word causes the issue. The two thread dumps in Dump201012120001InstantHang.txt were after a freeze just double clicking on a java source file on the project list. Project scanning was still in process. An editor tab opened with the filename, but no text and no further repaints. This has rendered the nightly build essentially useless. Any work has to be done with 6.9.1
*** This bug has been marked as a duplicate of bug 192548 ***
For the record, the first thread dump seems like a duplicate of bug #192653.
This is Swing's own manifestation of the problem with JComponent.repaint() requesting AWT-tree-lock (as described in issue #192548). See "Comment #2 From aquaglia" log with thread dump (asynchronous HTMLDocument's load by SwingWorker's thread): "SwingWorker-pool-2-thread-1" daemon prio=6 tid=0x042f1c00 nid=0x1210 waiting for monitor entry [0x0b5ae000] java.lang.Thread.State: BLOCKED (on object monitor) at java.awt.Component.getLocationOnScreen(Component.java:1995) - waiting to lock <0x1893a8c0> (a java.awt.Component$AWTTreeLock) at javax.swing.SwingUtilities.convertPointToScreen(SwingUtilities.java:380) owning HTMLDocument's write-lock (doing doc.fireInsertUpdate()) and calling java.awt.Component.repaint(Component.java:3221) which (with the current jdk) leads to acquiring of AWT-tree-lock. And this thread is deadlocked with "AWT-EventQueue-0" prio=6 tid=0x04436000 nid=0x11ac in Object.wait() [0x06f7e000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x19e67a50> (a javax.swing.text.html.HTMLDocument) at java.lang.Object.wait(Object.java:504) at javax.swing.text.AbstractDocument.readLock(AbstractDocument.java:1387) owning AWT-tree-lock and trying to acquire read-lock of HTMLDocument which blocks on the previous thread's ownership of write-lock on the same document. There is just JDK's own code involved so we should file an issue against JDK for this problem.
Since this is basically a JDK issue I mark it as WONTFIX.