top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

SVN crashed on Windows during a long operation

0 votes
360 views

I received the following message when running SVN UPDATE --SET-DEPTH INFINITY on Windows (build 1.8.9 downloaded from VisualSVN site):

THIS APPLICATION HAS HALTED DUE TO AN UNEXPECTED ERROR. 
A CRASH REPORT AND MINIDUMP FILE WERE SAVED TO DISK, YOU CAN FIND THEM HERE: 
   ....

This seems to happen only when downloading many large files (like third-party DLLs) or many, many small files (I am guessing about 3000 files). This seems to be a problem with 1.8 as 1.7 never did this (again my guess)

I have also tried the svn included with 1.8.7 version of TortoiseSVN and it pops up the "encountered an error and needs to close" message.

Any suggestion on how to solve this?

posted May 28, 2014 by Sonu Jindal

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
0 votes

I am looking to integrate SVN support into a Windows application. This application comes as both 32bit and 64bit versions and therefore I would need to have 64bit libraries. I have trouble finding the binaries for Windows 64bit development.

I would not mind compiling one myself, but it seems instructions are sparse and do not directly pertain to 64bit, perhaps because most people are just interested in the clients and 32bit is just fine there for most uses.

Thanks in advance?

+1 vote

Any thoughts regarding supporting symlinks in SVN on Windows? Windows has supported symlinks since Vista:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa365680(v=vs.85).aspx

Supporting cross-platform symlinks where possible will ease some compatibility pain for cross-platform development.

+5 votes

Are there side effects from applying the same svn merge --record-only on the same revision number and a new commit each time it is applied ?

Would there be issues with SVN mergeinfo and/or SVN in general if one keeps applying svn merge --record-only on a revision number repeatedly and commit in a svn merge --record-only followed by commit followed by svn merge --record-only followed by commit and the next cycle begins ? Its not an infinite loop svn merge; it would stop at some point.

0 votes

I just moved a subversion repository from an ubuntu linux 12.04 server running subversion 1.6.12 to an ubuntu Linux 14.04.1 server running subversion 1.8.8.

I have been able to export the code to an ubuntu 14.04.1 client running subversion 1.8.8 and when I do a
svn -u status
W155007: ‘home/xxx/src/trunk/c/eco’ is not a working copy

I get this error no matter what directory I do it in and it used to work fine before the move when we were running Ubuntu 12.04 clients with the old repository.

We are using apache2 with ssl for old and new repository.

0 votes

Is there a limitation in size on the property value that can be set? Any scalability traps to be aware of (i.e. non-linear increase in time due to increase in size of the property value)? I tried a 4Mb property, seems to work fine...

...