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 100226-556bb3edab59) VM: Java HotSpot(TM) Client VM, 16.0-b13, Java(TM) SE Runtime Environment, 1.6.0_18-b07 OS: Linux User Comments: jglick: Alt-Shift-PERIOD during classpath scanning. IDE froze for several minutes. WARNING [org.netbeans.modules.parsing.impl.TaskProcessor]: ParserManager.parse called in AWT event thread by: org.netbeans.modules.editor.java.SelectCodeElementAction$SelectionHandler.selectNext(SelectCodeElementAction.java:147) GUEST: my editor gets stuck all the time. Also file scanning runs forever and never finishes. I now mainly use netbeans for grails work. I have moved everything else to the eclipse for this reason. Maximum slowness yet reported was 158859 ms, average is 89304
Created attachment 94591 [details] nps snapshot
SelectCodeElementAction rescheduled outside of AWT event dispatch thread. http://hg.netbeans.org/jet-main/rev/26124b7c7840 Another problem that can be seen from the nps snapshot is that Schema2BeansProcessor.process takes almost 18% of the project scanning time.
Integrated into 'main-golden', will be available in build *201003040200* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/26124b7c7840 User: Dusan Balek <dbalek@netbeans.org> Log: Issue #181309 - SelectCodeElementAction should not be called from AWT event dispatch thread.
(In reply to comment #2) > SelectCodeElementAction rescheduled outside of AWT event dispatch thread. > http://hg.netbeans.org/jet-main/rev/26124b7c7840 > > Another problem that can be seen from the nps snapshot is that > Schema2BeansProcessor.process takes almost 18% of the project scanning time. Most of the time of this 18% is spend in native IO operations.