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

Re: Weird handle lock by tortoiseproc.exe log windows...

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2006-09-10 10:23:42 CEST

Peter Yamamoto wrote:
> I had two svn logs open on local workspaces.
> My tortoise settings have exclude *, include a couple local workspaces.
> When I browsed to a network mapped drive to rename a folder I couldn't.
> procexp.exe showed that each "tortoiseproc.exe" had a handle on the
> directory I had browsed to (it is completely unrelated to any version
> control directory/drive etc).
> When I closed the two svn log windows I could rename the folder.
> Weird.
> Peter

Not really weird if you know why that happens:

The handle you see TortoiseProc having open on that folder in
procexp.exe is the applications 'current directory'. That's the
directory the application was started from (not the one it is installed
in!). For example, if you open a DOS box on c:\ and then type
c:\program files\bin\TortoiseProc.exe /command:settings
you will see that TortoiseProc.exe will have a handle open to "C:\". And
that's not just TortoiseProc.exe, that happens with *every* exe there
is. Windows opens that handle for every application.

Now, TortoiseProc.exe is usually started from the explorer. And explorer
has a weird (ok, maybe not weird but just not documented) way of
deciding what the 'current directory' is.

I don't think there's much we can do about that. Sure, we could make
TortoiseProc.exe always set the current directory to a known path, but
which one?


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Sun Sep 10 10:23:52 2006

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

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