My co-workers and I are using 2.02 client to access 2.02 server. We've got a folder with a hundred or so files in it. When I do a GetLatestVersion recursively on this folder (and others like it in size), Windows Explorer tanks. It seems as thought The "Get" succeeds, but explorer crashes then reloads, then crashes, then reloads. . . most irritating.
Has anyone else seen this? Any ideas?
Explorer crashes during GetLatestVersions of
Moderator: SourceGear
I haven't heard of this problem, or anything similar, happening to Vault users. What filesystem are you using (FAT32, NTFS, SMB)?
Vault uses the .NET FileSystemWatcher class to monitor working folders for changes. The underlying mechanism is a Windows kernel feature that Explorer most likely also uses to keep its display up to date. The FileSystemWatcher documentation warns that there is only limited kernel buffer memory available to signal applications that new changes have arrived. Maybe Explorer or Windows is crashing with the additional watcher load from Vault.
You may be able to test that it's not something Vault specific, but filesystem update specific by running a task that continually updates files in a folder that Explorer is showing. If you have cygwin installed, you could simply "touch *" in a folder and its subfolders while Explorer is open.
Vault uses the .NET FileSystemWatcher class to monitor working folders for changes. The underlying mechanism is a Windows kernel feature that Explorer most likely also uses to keep its display up to date. The FileSystemWatcher documentation warns that there is only limited kernel buffer memory available to signal applications that new changes have arrived. Maybe Explorer or Windows is crashing with the additional watcher load from Vault.
You may be able to test that it's not something Vault specific, but filesystem update specific by running a task that continually updates files in a folder that Explorer is showing. If you have cygwin installed, you could simply "touch *" in a folder and its subfolders while Explorer is open.
Shaw Terwilliger
SourceGear LLC
`echo sterwill5sourcegear6com | tr 56 @.`
SourceGear LLC
`echo sterwill5sourcegear6com | tr 56 @.`
Post subject: Explorer crashes during GetLatestVersions of
Initially we were using a mapped Netware drive. After reading your post I thought I'd try a local drive (NTFS). I get the same error either way.
Testing completed without error.
We did the testing you suggested, but couldn't recreate the error. It seems that if there were a problem in the Windows kernel feature, then it would most likely be a corruption or a flaw in the Windows kernel. If it were corruption I think it would be unlikely that all three of us would get it at once. If it were a flaw, then you would be seeing this behavior on your other clients machines.
We've uninstalled and reinstalled the client, but still have the same behavior.
Any suggestions?
We've uninstalled and reinstalled the client, but still have the same behavior.
Any suggestions?
sterwill wrote:I haven't heard of this problem, or anything similar, happening to Vault users. What filesystem are you using (FAT32, NTFS, SMB)?
Vault uses the .NET FileSystemWatcher class to monitor working folders for changes. The underlying mechanism is a Windows kernel feature that Explorer most likely also uses to keep its display up to date. The FileSystemWatcher documentation warns that there is only limited kernel buffer memory available to signal applications that new changes have arrived. Maybe Explorer or Windows is crashing with the additional watcher load from Vault.
You may be able to test that it's not something Vault specific, but filesystem update specific by running a task that continually updates files in a folder that Explorer is showing. If you have cygwin installed, you could simply "touch *" in a folder and its subfolders while Explorer is open.