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.
Created attachment 110122 [details] profile of ide If I have more than 2-3 projects open, Netbeans regularly disappears into scanning projects forever. This makes the ide extremely unusable. I have tried increasing the max memory for the JVM to 2G from the 768M it was allocating itself on startup. This does not appear to have helped. I have netbeans and my source all on an SSD so I would expect it to be extremely fast. All my projects are Maven projects in case that has any bearing on the problem. JVM: Java(TM) SE Runtime Environment (build 1.6.0_23-b05) Java HotSpot(TM) Client VM (build 19.0-b09, mixed mode, sharing)
Created attachment 110123 [details] messages log file
According to attached nps file the scan time is spent in the AnnotationModelHelper$ClassIndexListenerImpl.typesChanged(). This listener eagerly creates and resolves all types with a new parser. The listener should not be eager but lazy. Maybe already fixed as I remember that Denis did some fixes in this area.
Denis, can you comment?
(In reply to comment #2) > According to attached nps file the scan time is spent in the > AnnotationModelHelper$ClassIndexListenerImpl.typesChanged(). This listener > eagerly creates and resolves all types with a new parser. The listener should > not be eager but lazy. > Maybe already fixed as I remember that Denis did some fixes in this area. AnnotationModelHelper$ClassIndexListenerImpl is a generic implementation for any annotation based j2ee metamodel. I haven't changed class index based types update functionality. > The listener should not be eager but lazy. I don't understand what it means. Could you please clarify what you meant ?
Tomas, can you please answer Denis's question? Not sure if this is still an issue, or if this can be closed.
Everything is already written in comment #2 and snapshot attached in comment #1. This listener eagerly creates and resolves all types with a new parser. Simply the listener should not load the jx.l.m.Elements unless it really needs them which is not the case. Definitely it should not be closed if it was not resolved yet.
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss