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

Memory leak with 1.6.x clients

From: Brian Osmus <osmusb_at_yahoo.com>
Date: Wed, 20 May 2009 13:05:26 -0700 (PDT)

A new Memory leak created in 1.6.x
client versions. When trying to commit ~33 K files the SVN client allocates approximately
0.5MB of memory for each file this quickly depletes the memory and swap space.
As a result, the OS kills the SVN client. Tried to do the commit several times with
1.6..1 client then attempted with 1.6.2 client giving the same result. In case the sandbox had become corrupted,
created a new sandbox using a 1.6.2 client and applied all the changes to it,
again with the same result. Then ran the python script to convert the local
copy for the 1.5.4 client. The commit
worked with the 1.5.4 client.
I did find a post about this same
issue under the user’s forum and somebody pointed bug #1964 which has been open
since 2004 but I was able to commit my changes without error using 1.5.4 with
the same exact client configuration, so it stands to reason that this is a new
bug. This is not a repeat of another bug report.
OS: Red Hat Enterprise Linux 4 (Update 7)
SVN Version: used the CollabNet Red Hat 1.6.1 and 1.6.2 rpms
Other: the system had 2GB of memory.
To reproduce this issue create a new repository and check in
an older Linux Kernel 2.6 once that is done get a newer Linux Kernel 2.6 and merge that with what you checked in. Then
do the svn commit and watch top. Notice the memory use for the process
increasing rapidly as the dots are displayed by the process. In my case, OOM killed the process with a -9.

Received on 2009-05-20 22:17:48 CEST

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