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.
Even though I disabled Source auto-scanning in options/misc/files I see it happen every time I build a project (huge cpu load and system is slow for some time), in stack trace - refresh recursive listeners...
Egor, can you please attach the stack trace. Thanks!
Created attachment 133243 [details] several thread dumps right after build I was mistaken about recursive listeners, it is FileUtil.refreshAll
org.apache.tools.ant.module.bridge.impl.BridgeImpl requested refreshAll, so filesystems are doing refresh all. Is it a problem? On all systems or on Solaris only (I suspect you don't have native listeners on Solaris turned on). Anyway the only Ant support can stop requesting refreshAll. Passing to Ant.
I saw that on Solaris with disabled sources auto-scanning, so I guess the bug is that BridgeImpl does not honor "sources auto-scanning" setting. On a system without native listeners every call to refreshAll may produce huge load on filesystem and slow everything the IDE down for several minutes.
(In reply to comment #4) > I saw that on Solaris with disabled sources auto-scanning, so I guess the bug > is that BridgeImpl does not honor "sources auto-scanning" setting. On a system > without native listeners every call to refreshAll may produce huge load on > filesystem and slow everything the IDE down for several minutes. sources auto-scanning is likely unrelated to the filesystem level calls. If it is, it should be handled on the filesystem's internals side, not on the API client side (ant) - back to P4, I don't see the reason above as justified to increase priority
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