TGitCache and TSVNCache don't play well together
By tortoise... on November 18, 2011 16:27 (imported from Google Code)
Reported on the TSVN mailing list:
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2880628
I could reproduce the problem on my machine by simply checking out the TGit source from Google Code, and then wait.
my directory structure is:
d:\development
d:\development\svnwc1
d:\development\svnwc2
d:\development\svnwc3
...
d:\development\tgitwc
that's enough to trigger this issue. No changes at all in the TGit working copy (all 'normal' overlays).
Had to wait almost 30 minutes until the issue showed up. Then attached the debugger to the TSVNCache.exe process:
- explorer asks for overlay status repeatedly for all folders in d:\development
- TSVNCache.exe does not send any shell notifications but only returns the asked status. It doesn't even crawl the working copies because there's no CPU left to do that (that thread has low priority and doesn't get a chance to run under those conditions)
- TGitCache as far as I can see from the source doesn't have a way to enable debug outputs in a release build, so I'm not sure what it does exactly, but I have to assume that this is the process that sends the shell notifications.
- TSVNCache.exe uses 0.47% CPU, while TGitCache.exe uses 32.87% (dual core).
maybe a TGit developer can reproduce this and attach a debugger to the TGitCache.exe process...