[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [TSVN] Explorer hangups

From: Molle Bestefich <molle.bestefich_at_gmail.com>
Date: 2005-04-01 14:50:04 CEST

SteveKing wrote:
>
> You could still use the latest nightly. Just copy TSVNCache.exe and
> TSVNCache.pdb to a save location, then downgrade to 2923, then replace
> those two files of the older version with the version you just saved.
>

Thanks!

The 2946 nightly works great in the debugger, and it locks up like the old
ones used to.

Thanks again :-D.

I'm still perfecting my debugging skills, so apologies to everybody for the
noise I'm generating.

Here's what I've got so far by:
- kill --force TSVNCache
- right-click folder (causes explorer to hang)
- fire up visual studio, attach to tsvncache process.

Only one of the four threads seem to be doing something actively.
It's the WndMain/WndProc() thread spinning around inside while (bRun) { ...
}.
The others seem to be hung, judged by:
- every time I pause the cache process, they are at the same source
location...

Details on where they *seem* to be sort-of stuck:

PipeThread:
PipeThread():
fConnected = ConnectNamedPipe(hPipe, NULL) ? TRUE : (GetLastError() ==
ERROR_PIPE_CONNECTED);

InstanceThread:
CloneData():
if( !pData->IsLocked() && (pNewStringMgr == pData->pStringMgr) )

CFolderCrawler :
CloneData():
workingPath = m_foldersToUpdate.front();

WndProc:
WinMain():
while (bRun) { ... }

I'm thinking that PipeThread and WndProc is fine, they're supposed to
sit+spin there.

But CFolderCrawler and InstanceThread seems to me like they should be moving
on, and they're not...
Hmmmmm.......

Please give me more information if you have anything to offer (esp. you
Steve ^_^).

I'll be working on trying to figure out how the cache works and what goes
wrong myself in the meanwhile...
Received on Fri Apr 1 14:50:47 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.