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.
When I right click on a directory to bring up the context menu that contains a number of sub directories ( 2000 java files in a number of packages). The IDE locks up for a number of minutes. It does come back in the end and there is no exception shown. The context menu appears and we continue working.
Can you attach a thread dump generated during the time when IDE is displaying the menu? BTW: Is it local directory or a resource connect from network?
Created attachment 42580 [details] 3 x kill -3 output while the IDE is not responding after right clicking on directory
Created attachment 42581 [details] Screen Shot of IDE before context menu has appeared.
PS. These are local directories.
Created attachment 42582 [details] Faster after I disabled all the Ruby modules. (still a little slow on first click)
Thanks for trhead-dumps, this is helpful. I see o.n.m.ruby.RubyMimeResolver.readHeader on FolderRecognizer thread, but the main overhead is (in my opinion) UML .. see AWT-thread : o.n.m.uml.integration.netbeans.actions.ReverseEngineerAction.findJavaFiles
Right, the deep scan of directory tree performed during action enabling is really a killer.
*** Issue 106552 has been marked as a duplicate of this issue. ***
Is it uml issue? I'm working with 070608 build now without uml,ruby etc and got delayed reactions quite often (for example I restart netbeans and tried context menu on my src of my module, and wait for 10 seconds before context menu appears, tried package context menu next and wait may be 20 seconds)
sorry, I have uml, but don't remember when it was integrated if was (may be uml is integrated by default ant task in nbbuild now..)
The enabling logic used to get a list of ALL Java files from the selected nodes, in this particular case, there was a deadlock in Node.getChildren(). Apart from the deadlock, folder deep scanning is a heavy process that should not be used in enabling anyway. Made changes to enable/display 'Reverse Engineer' menu item on 1. project node (only one) that defines Java source groups 2. Java file nodes or folder nodes that are under Java source root folders for the same project, without deep scanning If project node is selected, it supersedes selection of java file node or folder node, so that RE will be performed based on selection of project source groups.
verified in netbeans-hudson-trunk-1023-full (Build 070621)