Subversion checkout fails with ACCESS_VIOLATION in svn_wc_add_repos_file4()

Here is the related thread in dev@ Subversion mailing list.

It looks like your server interrupts the connection and Subversion 1.8 client built with serf 1.3.5 library crashes on this failure. That's why you see the error with older Subversion client but the client built with serf 1.3.5 crashes.

Serf 1.3.5 fails to process the error and thus crash on the client occurs. There is a great chance that the crash is caused by the bug in Serf library (on client side) which is fixed in the version 1.3.6:

Revert r2319 from serf 1.3.5: this change was making serf call handle_response multiple times in case of an error response, leading to unexpected behavior.

I suggest trying Subversion command-line client which is built against Serf 1.3.6. Subversion 1.8.x binaries built with serf 1.3.6 are going to be available soon.

I posted the same dump file to the users@subversion.apache.org mailing list but have had no reply in 2 weeks. To get around this issue, I switched QuickBuild to use jsvn.bat from the pure Java distribution of SVNKit and the issue seems to be resolved. Jsvn has the same command-line interface as the Apache svn binary, so it's a simple drop-in replacement.

I initially had an authentication issue because we use NTLM to authenticate with our active directory. The error was "svn: E170001: Authentication required for repsoitory" The solution was to add the following to svnkit\bin\jsvn.bat after the existing EXTRA_JVM_ARGUMENTS environment variable:

rem Adding this to resolve authentication issue as per http://subversion.1072662.n5.nabble.com/SVN-authentication-problem-td1560.htmlset EXTRA_JVM_ARGUMENTS=%EXTRA_JVM_ARGUMENTS% "-Dsvnkit.http.methods=Basic,Digest,Negotiate,NTLM"

The only thing worked for me is to install the previous version of Tortoise svn(TortoiseSVN-1.8.6.25419-x64-svn-1.8.8) which runs with the pervious version of svn client 1.8.8 and then use the old version of the svn.exe. That worked against the newer version of the server (1.8.9) too.

(I had the same issue. I upgraded yesterday my collabnet subversion to the latest (svn version 1.8.9-3871.129) and both the command prompt svn checkout or the latest tortoise svn (1.8.7) fails. I have the same ACCESS_VIOLATION error in the dump log. And my computer is Windows 7 64 bit.)