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.
Build: NetBeans IDE Dev (Build 100114-5210d70aa322) VM: Java HotSpot(TM) Client VM, 14.3-b01, Java(TM) SE Runtime Environment, 1.6.0_17-b04 OS: Linux, 2.6.31-17-generic, i386 Maximum slowness yet reported was 479905 ms, average is 479905
Created attachment 93300 [details] nps snapshot
100114-5210d70aa322, JDK 6, Ubuntu. I guess I must have typed Ctrl-K or similar; the IDE suddenly froze with 100% CPU and does not recover. Was able to restore my session only using jrunscriptin.kenai.com and Thread.kill on AWT-EventQueue-1.
Created attachment 93301 [details] Thread dumps of hang
I see. It happens when you use Ctrl+K and have some documents cloned in two or more editors. I'll fix it. In the mean time please refrain from cloning documents and the action should work fine.
http://hg.netbeans.org/jet-main/rev/d29aa51d3459
(In reply to comment #4) > It happens when you use Ctrl+K and have some documents cloned in two or > more editors. I never clone windows and I'm pretty sure this was not the case when I ran into this bug. (As I mentioned, I managed to recover the IDE by killing the EQ thread, and I would have noticed and reported such an unusual situation as a duplicated window if that had happened somehow by accident.)
Haven't tried with your patch yet, but I just got this freeze for the third time when trying to get word completion; lost some work the second time.
Created attachment 93355 [details] nps snapshot Trying to complete a symbol.
BTW in contrib #01d54f87da5f I am adding a feature to the autosave module to interrupt the event dispatch thread if it freezes for too long. Should help avoid data loss from actions which go into endless loops in EQ.
(In reply to comment #9) > in contrib #01d54f87da5f I am adding a feature Reverted in favor of bug #179597.
(In reply to comment #6) > (In reply to comment #4) > > It happens when you use Ctrl+K and have some documents cloned in two or > > more editors. > > I never clone windows [...] Ok, maybe there are several ways how to reproduce this bug. Cloning windows was the way that reliably reproduced it for me. I believe that d29aa51d3459 fixes the problem. Unfortunately it does not seem to be in main-golden yet.
(In reply to comment #11) > Unfortunately it does not seem to be in main-golden yet. Nor in main-silver; jet-main has been broken for days. Ask RE for emergency assistance.
(In reply to comment #12) > (In reply to comment #11) > > Unfortunately it does not seem to be in main-golden yet. > > Nor in main-silver; jet-main has been broken for days. Ask RE for emergency > assistance. jet-main is fine, but bertram.netbeans.org has recently been down too often which affected builds and fixes propagation.
Integrated into 'main-golden', will be available in build *201001240200* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/d29aa51d3459 User: Vita Stejskal <vstejskal@netbeans.org> Log: #179519: EditorRegistry.componentList may contain editors that visualize the same document (eg. when the document is cloned to multiple editors), but getNextDoc has to operate only on the documents