top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

svn log hang after upgrade from version 1.7.5 to 1.8.3

+1 vote

I recently upgraded my Subversion client from version 1.7.5 to 1.8.3 and from that time on I experience hangs when executing multiple 'svn log' commands in a short amount of time. The "hanging" svn process consumes all CPU cycles it gets but never finishes.

I can reproduce the problem using the following shell script (on Windows using Cygwin):

for DIR in $(svn ls "${ROOT}" | head -n 4); do
 svn log -v -l 5 "${ROOT}/${DIR}" 2>&1 | head -n 100 > /dev/null

In my environment I need at least 4 svn processes to achieve the faulty behavior. The hang only occurs if the output is truncated using the head command (but it can be redirected to a normal file instead of /dev/null which then contains the expected log messages).

posted Oct 16, 2013 by Mandeep Sehgal

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

It seems like issue #4425 [ ] which is fixed in r1522892 and proposed for backport to Subversion 1.8.4.

answer Oct 16, 2013 by Luv Kumar
I tried the nightly build of TortoiseSVN [1]

svn, version 1.8.4-dev (under development) compiled Oct 16 2013, 23:05:56 on x86-microsoft-windows

(as I was not able to compile the 1.8.x branch myself using Visual Studio 2008 because of a weird include path issue and the Subversion nightly build site delivers only a 404 page) and I was not able to reproduce the issue using my test case so I guess it is fixed.
Similar Questions
+2 votes

Currently svn log will display file changes and svn:externals property changes, but will not display changes made to the file pointed at by the external. For example, if a user commits a change to a file external, svn log will show that the properties reflects a new revision of the file is now being referenced, but will not see commit made to the file, even if it was done from the current WC.

It would be a very useful feature to have svn log include the log of the file external(s) as if it were a formal vile within the WC (even if it required a switch --include-externals) to enable.

+1 vote

I am running subversion 1.4.2 server with apache 2.2.14 on Linux machine. Now I want to upgrade to subversion 1.8.8 with apache 2.2.25 . Please guide me how to upgrade?

0 votes

I wanted to know what are the best practices/process to be followed if we are planning to migrate some legacy code in Java 1.3/1.4 to the latest version ie Java 8.

0 votes

I'm trying to figure out how to migrate our existing SVN 1.3.1 repository to another server. It's on a Jumpbox with TRAC.

I followed the instructions and have setup svnsync, but since it's pre 1.4 it's setting at revision 0 and not migrating.

I then setup subgit as a way to get it and them migrate it back to the new server, but subgit says it translated 2541 revisions, but there's nothing in the git repository as far as I can tell.

I even tried using the Revision Control Turmkey Linux box with svn 1.6.17, but it gives me the same problems and I can't seem to get it upgraded to 1.8.9 to use svnrdump.

Does anyone have a suggestion on how to migrate svn 1.3.1 to 1.8.9 without console access?