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

Re: "svn blame -g" causing svnserve to hang & mem usage to hit 2GB

From: Paul Burba <ptburba_at_gmail.com>
Date: Mon, 8 Nov 2010 09:13:59 -0500

On Thu, Nov 4, 2010 at 8:59 PM, Chris Tashjian <ctash_at_thepond.com> wrote:
> I posted this on the users list, but I'm confident that this is a bug.
>
> Background:
> For a while now (off and on for over a year, but more frequently in the last
> 6+ months) we've been having problems with svn "crashing", yet there's no
> error in the log file.  In talking to someone the users list it sounds like
> svn is actually just hanging.  Clients get the following response:
>
>   svn: Can't connect to host 'svn': No connection could be made
>   because the target machine actively refused it.
>
> Our repository has 129K revisions.  The format is "4 layout linear", it was
> created with svnadmin 1.4.x and has since had "svnadmin upgrade" run both in
> 1.5 and 1.6.  We're currently running SlikSVN 1.6.13 (Win32), but I have
> previously had this problem dating back to versions of 1.5, both stock and
> from CollabNet.  The issue now happens numerous times per day and it looks
> like I've discovered why....
>
>
> As a test I ran "svn blame -g" on a file with a bunch of revisions and
> watched memory usage on the server spin up to 2GB.

Chris,

By a "bunch of revisions" what exactly do you mean? Many revisions
which were the result of a merge? Or simply many changes made
directly to the file (not the result of a merge)?

> Paul - I'll see if I can get a test repo up with the error. In the
> meantime, would a copy of the svn:mergeinfo help?

Any luck? I should have asked this out of the gate (though I'm sure I
know the answer): Is your repos public? Obviously the most direct
route to replicating this would be with a copy of your actual data :-)

Paul
Received on 2010-11-08 15:14:38 CET

This is an archived mail posted to the Subversion Dev mailing list.

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