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.
The "Open Type" dialog (CTRL-O from the editor) needs quite some time to find classes satisfying the entered search criteria. My project has about 500 custom classes with a lot more in the classpath. (Spring, Hibernate, Axis, Commons, etc ...) It would really improve the usage of the editor if this dialog would show up faster classes. Maybe first searching in the custom classes and while showing the results of this search saerching for matches in the classpath.
Is it slow first time you invoke "go to type dialog" or every time? First time it is noticeably slower because of opening indexes. If you have many class-path roots and classes, it can take some time. Are you using dev builds? When your search is in progress, press Alt-Shift-Y (last icon in toolbar in dev builds). When it shows the result, press Alt-Shift-Y again. It will create a profiler snapshot, attach it here. Thanks. Are your sources on network drive or local disk? Do you use J2SE project or another one? Is the scan in progress?
No dev builds. Just the beta that was released recently. Should I try a dev build to check whether it's the case ? I might be wrong, but in NB 6.5 this was REALLY slow all the time. It looks to me 6.7beta has made some progress here. But it's still quite slow. Everytime. I have to admit I don't notice the initial time it's supposed to be slower. All sources are stored locally. The classpath jars are all maven artifacts of a local repository. The project is a Maven project - backed by a local 2.1.0 installation. Everything runs in J2SE 1.6.0b12. I'll try to get this thread dump uploaded. Good to know there's a shortcut because I can't click on anything when the IDE's busy.
There were many optimisations in 7.2. It is much faster now. See http://wiki.netbeans.org/NetBeans_72_NewAndNoteworthy#Background_Indexing {quote} Background Indexing The indexes and indexing infrastructure were rewritten to use transactions. The project scanning and up to date check do not block editor features nor navigation. These features use the previous committed index. Also the write transactions are suspended by read transactions, so the background indexing has lower priority than user actions. Parallel Indexers The binary indexers run in parallel which makes indexing of java project faster. {quote} @Dusan Balek: I think, this issue can be closed.
Set target-milestone of open issue to TBD (was < 7.3, f.e. 6.8), so the issue doesn't get lost.
Set target-milestone of open issue to TBD (was < 7.3, f.e. 6.8), so the issue doesn't get lost. This time the target milestone is really set.