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: - I do not have any repository - have opened a project - clicked on Team main menu item - selected History And got 2 accesses to file system from EDT, which could freeze UI if slow NFS file system is used. See stacktrace attached.
Created attachment 124808 [details] stacktrace
there was no slowness report in the actions 5 years existence. this is just hypothetical. lets deal with it when the real need appears.
AFAIK slowness detector is set to detect more than 2 seconds delay. I think that for main menu even 1 second it too much. And most probably not many people use the menu for nfs mounted projects.
please look at the http://statistics.netbeans.org/analytics/detail.do?id=176199
> please look at the http://statistics.netbeans.org/analytics/detail.do?id=176199 where is the relevance? this issue states the problem is fs access in EDT while all the snapshots point at a problem in git.getActions()! and anyway, the issue #221202 covering report 176199 was fixed.
sorry, icorrect link. Here it is: http://statistics.netbeans.org/analytics/detail.do?id=195205
(In reply to comment #6) > sorry, icorrect link. > Here it is: > http://statistics.netbeans.org/analytics/detail.do?id=195205 is this a valid setup you normally use? how is it possible to properly use the IDE when already isFile() takes 15 seconds? or is it just like already mentioned in comment #2 - hypothetical and artificial scenario to prove the point?
the project I'm trying to use in on slow NFS share and the real problem is that even if I'm not interested in history but hovered history menu accidentally I could get an IDE freeze
the same as #223507 i guess *** This bug has been marked as a duplicate of bug 223507 ***