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 100412-2e53179720ff) VM: Java HotSpot(TM) Client VM, 10.0-b19, Java(TM) SE Runtime Environment, 1.6.0_04-b12 OS: Windows XP User Comments: GUEST: Clicking in the text editor Maximum slowness yet reported was 5295 ms, average is 4280
Created attachment 97119 [details] nps snapshot
I am looking at: http://statistics.netbeans.org/exceptions/exception.do?id=312087 The 3s are spend in org.netbeans.modules.editor.NbEditorKit$NbBuildPopupMenuAction.buildPopupMenu() and are then split into various insignificant times all over including querying lookup, classloading, etc. I think the simplest way to get UI responsiveness here is to apply "do sooner" rule. Could the popup menu of the editor (defined per EditorKit, if I am not mistaken) be built while prloading the NbEditorKit in its call() method? Creating actions outside EQ thread shall be possible. Calling their isEnabled method is not, but that could be possibly done one by one in invokeLater...
Created attachment 98392 [details] nps snapshot
*** Bug 213426 has been marked as a duplicate of this bug. ***
I've added code preload into NbEditorKit.call(), the actions are actually instantiated + instruction built how to create a popup menu from the instances, but since proper use of the pre-created info (= caching) would require invalidation etc on SFS changes, I just load the instances and trash the data. Could be extended to caching implementation in the future. Fixed in http://hg.netbeans.org/jet-main/rev/c565304ea877
Integrated into 'main-silver', will be available in build *201307232300* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/c565304ea877 User: Svata Dedic <sdedic@netbeans.org> Log: #183946: Popup menu action code os preloaded after editor open