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.
I have ~50 projects opened (all CND projects), so full external changes check takes sometimes more than 30 seconds. That's fine. But as soon as I switch to IDE and back it starts again. Debuggin requires a lot of such switches and so for me it looks like IDE is in premanent external changes check. And no files really change.
Created attachment 99602 [details] snapshot Checking takes long but that's fine if only that was one time.
1. There is a way to disable the check and make it manual. 2. Give me logs: -J-Dorg.netbeans.core.ui.focus.level=FINE 3. Solaris users often use focus-follow mouse, which triggers the refresh quite often. Are not you using it too?
Created attachment 99675 [details] messages log with -J-Dorg.netbeans.core.ui.focus.level=FINE Refresh after start was taking ~7seconds then I started debug session and it jumped to 30-35 seconds non stop.
2 Jaroslav: 1. I tried to disable it but did not find how to run it when needed. Without being in sync with filesystem it is really hard to develop anything. 2. Attached 3. I do not use focus-follow mouse
BTW it looks like scanning continued several times even after I stayed in the IDE, does it cancel pending scan tasks or queue them on every focus change?
I've found it! Source/Scan for external changes! Unfortunately it also does projects rescan and so it takes ~10 times longer than simple external changes scan but finally I can control when to do it. Thanks! Anyway I still think that there is a bug that pending scan jobs are not canceled. And in general for me to check files on EVERY windowActivated is way too often. Maybe it's worth to have customizable frequency limit like "no more than once every X minutes" or something like that. Anyway thanks for mentioning manual mode, now I can finally develop productive.
I am glad the manual mode makes your experience better. There shall also be refresh in every folder popup menu, in case you know what you want to refresh. As far as I can see from your log file, there are lines like: Refresh done in 9,242 ms This means the refresh usually takes less than 10s!? That is exactly what we wanted to see. I think that is perfect. But you still seem to be bothered by frequency of the scan. You think the tasks are somehow accumulated and then run multiple times, not only when the window is activated. That is possible, as there is more: "Starting slow refresh" than "Window deactivated, preparing refresh task" I'll see whether I can think of something being wrong.
Vladimir created a sample application to reproduce the problem. It is tracked as bug 186655. *** This bug has been marked as a duplicate of bug 186655 ***