I'm on fresh Vista Ultimate installation and I noticed that %subj%
drains one CPU's core at 100 % continuosly since time I've opened
Windows Explorer and focused a folder on C: disk. If I focus folder
containing valid SVN working space, the cache stops draining CPU and
if I select another arbitrary folder C: or D: disk, it drains it
again.
In the past, I have a similiar problems with all versions after 1.4.5
(10425) and on the top of it, Windows Explorer time-to-time has
deadlocked e.g if I opened a folder. Restart of machine did not help.
An attempt to open the same folder ended with deadlock as well.
If I unistalled such version and install back 1.4.5 (10425),
everything worked smoothly each time.
###
Does anobody has a similiar experiences?
Thanks, Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-un...@tortoisesvn.tigris.org
For additional commands, e-mail: users...@tortoisesvn.tigris.org
Please try the build from http://nightlybuilds.tortoisesvn.net/1.5.x/
and check whether the issue is solved.
Stefan
-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
> Please try the build fromhttp://nightlybuilds.tortoisesvn.net/1.5.x/
> and check whether the issue is solved.
Hi Stefan,
I've  reinstalled TortoiseSVN by build 13390. If I opened Windows
Explorer and
select C: disk first time, I got error dialog with
"Unhandled Win32 exception in TSVNCache.exe [1708]".
but SVN cache itself keeps running and it seems it works (at least it
consumes
some CPU time and Client seems to work correctly). I will keep using
this build to
verify functionality...
###
In the change log I read a record concerning bugfix of SVN cache if
work space is in the root. But this is not the case.
FYI, each of my disks constain some folders
having "dotted" names, e.g. on my C: disk it is:
._
.0
.SVNBOX  // this is a local SVN repository
.VPCBOX  // this is a shared disk with Virtual PC
.WKS-PM // this is my workspace
Boot
Document and settings
...
Please try the next nightly build.
> > I've  reinstalled TortoiseSVN by build 13390. If I opened Windows
> > Explorer and
> > select C: disk first time, I got error dialog with
> >     "Unhandled Win32 exception in TSVNCache.exe [1708]".
> Please try the next nightly build.
I tried reinstall it with build 13403 and I got an error before
installation process has been finished:
    An error occured during installation of assembly
    component
    {241560EA-12B7-37C4-9724-DE33E7FE7BB7}
    HRESULT: 0x8007041D
http://geekswithblogs.net/jemimus/archive/2005/11/14/60064.aspx
> http://geekswithblogs.net/jemimus/archive/2005/11/14/60064.aspx
???
It just shows: Application Error. No error message available
Please make up your mind. Either you did get an error message as you
wrote before (quote: "I tried reinstall it with build 13403 and I got
an error before
installation process has been finished:
   An error occured during installation of assembly
   component
   {241560EA-12B7-37C4-9724-DE33E7FE7BB7}
   HRESULT: 0x8007041D
")
Or you didn't. So what is it?
I'm pretty sure he meant that the blog site you linked to was down
earlier on, as all I got was an error message from the server when I
tried visiting it this morning.
It's working now, though...
-- 
Kurt Bernhard Pruenner --- Haendelstrasse 17 --- 4020 Linz --- Austria
.......It might be written "Mindfuck", but it's spelt "L-A-I-N".......
Sorry, when I searched the web for the error code, that page was online.
Next time, instead of writing "???" please just mention that the page is 
not reachable - I'm not a mind reader.
> >>> It just shows: Application Error. No error message available
> Sorry, when I searched the web for the error code, that page was online.
> Next time, instead of writing "???" please just mention that the page is
> not reachable - I'm not a mind reader.
The problem is, that page *was* reachable: it responded with
unsightly logo and text:
Application Error. No error message available
hence I had no idea what you meant referring me to such page,
on the top of all residing on a some blog I don't use to read them...
Next time, I suggest to drop a simple message:
STFW for the error code
;-)
Peter
BTW, I retried to install build #13403 successfully, but currently
I have no time to test it.