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.
Every opened Java editor attached its own ParsingListener to a parsing support in Java module through reflection. Obvious problems: - Bad scaling. The more editors the more listeners invoked when anything is parsed. - Behaves poorly when any refactoring feature is called. Many sources can be parsed and again all listeners are notified though they may not be interested. - Misuse of API (unpublished!). It listens to more events than neceseary.
Probably affects long delay between the end of scaning and showing of results in a tree when find usages is called.
NbJavaFoldMaintainer is editor stuff.
NbJavaFoldManager is now rewritten to JMIs under issue 42255 and compares resources which should be reasonably fast.
I've meant it compares org.netbeans.jmi.javamodel.Resource instance from the event with the one for the fileobject of the edited dataobject.
Radime, can you please verify this issue? Thanks!