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.
Steps to reproduce: 1.Start IDE. 2.Open Favorites view 3.Add some NB CVS module (checked out previously) eg. java 4.Start Delete action on java folder. Now it takes a few minutes to delete. All nodes in Favorites view are collapsed and view is refreshed often during delete action. It should not happen as there is nothing to change in view - only underlying deep nodes are deleted not root nodes. Not sure if it should go to explorer or nodes.
There is too many VisibilityQuery ChangeEvents when deleting folder structure. According to Jarda surrounding line: private static void refreshVisibility() { if (instance != null) { instance.refreshVisibilityTask.schedule(100); } } by AtomicAction should solve this problem as events would be fired after whole delete operation would be finished.
Created attachment 49980 [details] Complete call stack
What is wrong with the stacktrace? It does not imply that the refresh is actually run - it is only being scheduled. I can increase scheduling delay to 1000 or so, we'll see if that helps. Regarding AtomicAction; this would have to be done several layers above CVS and synchronous callbacks involved here such as doDelete() would not be affected anyway.
Just try steps described above and you will see what is wrong. Too many events are comming to Favorites from VisibilityQuery during delete.
*** Issue 118268 has been marked as a duplicate of this issue. ***