QVCS/QVCS-Pro Bug in 3.8, Can lead to sluggish performance Options

[Jim Voris]

There is a bug in QVCS/QVCS-Pro 3.8.19 (and earlier 3.8 releases) that can lead to sluggish performance. See this thread for example.

The bug will be fixed in an upcoming 3.8.20 build, and will (of course) be fixed in 3.9.

Here's a fairly technical explanation for background:

The problem is caused by an attempt to get file status a non-existant file. For the problem files, the old checkout location (embedded within the individual archive files) is for a location on your network that likely no longer exists:

e.g. \\some non-existant machine name\share\.... etc.

In earlier releases, QVCS did not attempt to get file status on that location unless the file was locked by the current user. In 3.8 in some places in the code, it attempts to get file status on that file, irrespective of whether there is a lock on the file or not. This is a bug, and is the source of the sluggishness, since the file status request has to timeout waiting for the non-existant machine to respond.

The workaround:

Here's the workaround:

1. Navigate to the problem (sluggish) directory.
2. Wait for the the files to display. This may take some time.
3. Select all the unlocked files in that directory.
4. Lock all of those files.
5. Do an undo checkout on all the files you locked in step 4.

Repeat for all the directories where you have sluggishness.

The 3.8.20 build should be available before the end of July. I'll announce it here as well as on the Quma home page.