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 nbms-and-javadoc-3954-on-090919) VM: Java HotSpot(TM) Client VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01 OS: Windows XP, 5.1, x86 User Comments: stefan79: Opened a big java-src-file (~7500 lines) GUEST: Started NetBeans GUEST: Opened netbeans Maximum slowness yet reported was 9078 ms, average is 5034
Created attachment 88180 [details] nps snapshot
This issue already has 8 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=157644
I do not see anything suspicious. Visual part of editor initialization is performed in AWT thread. If I look deep into snapshot most of time is spent by class loading but I do not know if we can do anything with it. There are some warm up tasks to preload some classes but it is possible they are not yet done in this case. It looks like io is also used by another thread so there is clash and io throughput is low. Jarda any comment?
Note: Thread "Load Open Projects" also performs io. It looks like cold start so data are not in OS filesystem cache.
This issue already has 13 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=157644
This issue already has 21 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=157644
This issue already has 24 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=157644
There are apparently more different snapshots. Those which reference EditorContextDispatcher and it's call to getOpenedPanes() are caused by workaround done because of issue #172889. This was changed right before beta since I believe that it's more important to have working functionality than speed. It in fact removed the fix of issue #168415. As soon as issue #172889 is fixed, I'll remove getOpenedPanes() call again. So please, concentrate on other cases and ignore EditorContextDispatcher.
Build: NetBeans IDE Dev (Build 200908022240) VM: Java HotSpot(TM) Client VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01 OS: Windows XP, 5.1, x86 User Comments: Maximum slowness yet reported was 22406 ms, average is 6501
Created attachment 88792 [details] nps snapshot
I went through 44 duplicated reports in http://statistics.netbeans.org/exceptions/detail.do?id=157644 and removed those that do not contain word debugger. Still 25 issues is left. That still makes this issue P2. Reassigning to debuggerjpda to adjust its code. The openide.text did what it could by offering NbDocument.findRecentActivePane(...) the rest of the work needs to be done by debuggerjpda.
Since debugger does not call getEditorPanes() any more, it's already fixed.
I just tried to grep for the getOpenedPanes() calls and there still seem to be some of them (even in jpda and core debuggers). Can/shall those be eliminated as well? $ grep getOpenedPanes --include "*.java" *debugger* -r ant.debugger/src/org/netbeans/modules/ant/debugger/Utils.java: JEditorPane[] panes = editor.getOpenedPanes(); bpel.debugger.ui/src/org/netbeans/modules/bpel/debugger/ui/action/RunToCursorUtil.java: JEditorPane[] op = e.getOpenedPanes (); bpel.debugger.ui/src/org/netbeans/modules/bpel/debugger/ui/action/RunToCursorUtil.java: JEditorPane[] editorPanes = editorCookie.getOpenedPanes(); bpel.debugger.ui/src/org/netbeans/modules/bpel/debugger/ui/util/EditorUtil.java: final JEditorPane[] panes = editorCookie.getOpenedPanes(); cnd.debugger.gdb/src/org/netbeans/modules/cnd/debugger/gdb/disassembly/Disassembly.java: if (editorCookie.getOpenedPanes() == null) { debugger.jpda/src/org/netbeans/modules/debugger/jpda/actions/MethodChooser.java: JEditorPane[] openedPanes = ec.getOpenedPanes(); debugger.jpda.projects/src/org/netbeans/modules/debugger/jpda/projects/EditorContextImpl.java: JEditorPane[] eps = ec.getOpenedPanes(); debugger.jpda.projects/src/org/netbeans/modules/debugger/jpda/projects/RunToCursorActionProvider.java: //PATCH 57824: getOpenedPanes () calls from non AWT threads can python.debugger/src/org/netbeans/modules/python/debugger/Utils.java: JEditorPane[] op = editorCookie.getOpenedPanes(); spi.debugger.ui/src/org/netbeans/modules/debugger/ui/Utils.java: JEditorPane[] op = e.getOpenedPanes (); spi.debugger.ui/src/org/netbeans/modules/debugger/ui/Utils.java: JEditorPane[] op = e.getOpenedPanes (); spi.debugger.ui/src/org/netbeans/spi/debugger/ui/EditorContextDispatcher.java: // getOpenedPanes() MUST be called on AWT. spi.debugger.ui/src/org/netbeans/spi/debugger/ui/EditorContextDispatcher.java: // getOpenedPanes() MUST be called on AWT.
I've checked usages of CloneableEditorSupport.getOpenedPanes() before I've closed this and got no results. I've forgot about EditorCookie.getOpenedPanes() - this is used at several places. Should not this method be marked as deprecated if it must not be called?