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.
jdk-1.5 linux daily 24/8/2004 cvs, ext, ssh 1. go to Tools-->Options-->Source Creation and Management-->Version Control Settings 2. set 'Auto Refresh' to 'For Newly Opened Folders' (default) 3. add a cvs folder in versioning manager and check out a bunch of projects (i have 12) with some big stuff (lots of nested directories, etc). 4. restart IDE. 5! go to versioning tab and expand the cvs node. vcs winds up in a constant refresh loop. on the runtime tab, the commands 'Refresh' and 'LIST_STATUS_CMD' are repeated forever with no pause between them. i let it run overnight and it was still going strong.
setting the option to no refresh immediately stops the loop. setting the option back again will cause the loop to restart.
I have reproduced the problem, it looks like this happens when there is no CVS folder in the root of the working directory.
you may want to consider issue 48032, as this may fix this problem as well without requiring a CVS folder...
This was a regression. It was caused by some other fixes in status caching infrastructure. It's fixed in trunk: /cvs/vcscore/src/org/netbeans/modules/vcscore/caching/VcsCache.java,v <-- VcsCache.java new revision: 1.77; previous revision: 1.76 Issue #48032 seems to be specific for CVS integration, while this is a general problem that can occur with all VCS profiles.
will the fix require a CVS folder in the cvs folder (err, you know what i mean)?
:-) I know what do you mean. I'll evaluate this in issue #48032...
*** Issue 48128 has been marked as a duplicate of this issue. ***
this seems to be back with a vengeance in beta2. to reproduce: 1. add repository for netbeans in versioning manager. 2! check out 'stable'. endless refresh loop after checkout is done.
i strongly suggest adding a regression test...
sorry, actually, this only appears to happen after a checkout. not the same bug, although very similar. shoud i open no issue or keep on this one?
The core of the problem might be similar. I'll look at it...
Alvin, the refresh that is executed after the checkout does not seem to run in a loop. It's true that there are a lot of refresh commands running, but every refresh is for a different folder. You can verify this in Runtime. After some time all refreshing stopped (do not know exactly how long did it take, sice I left it running on background). Anyway, the IDE is usable while Refreshes are running, so it should not block your work. The refresh after checkout is not implemented very efficiently. Therefore this is a duplicate of issue #32345. It concerns both checkout and update commands. *** This issue has been marked as a duplicate of 32345 ***
Verified.