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

Re: Suspected Memory Leak for merge

From: John Szakmeister <john_at_szakmeister.net>
Date: 2005-07-29 23:38:28 CEST

On Thursday 28 July 2005 17:15, Mike Joseph wrote:
> On Wed, Jul 13, 2005 at 02:12:47AM -0400, John Szakmeister wrote:
> > On Wednesday 13 July 2005 01:30, Brian Buesker wrote:
> > > Sorry, I forgot to attach the log. Here it is.
> >
> > I have proposed a change for the 1.2 branch that clears up quite a bit of
> > the memory usage in merge operations (r15233). Would you care to try the
> > current Subversion trunk/?
> >
> > -John
>
> I have been experiencing a similar problem with the svn client allocating
> all available memory and getting killed while attempting a large merge:
>
> 20781 mj 18 0 2301m 373m 2604 R 16.5 74.0 5:00.87 svn
>
> Note that that is indeed 2.3 GB of memory!
>
> I haven't been able to try the patch yet, but I did put together a test
> repository which can be used to reproduce the problem with any svn client:
>
> svn checkout https://svn.doze.net/memleak/trunk
> cd trunk
> svn merge https://svn.doze.net/memleak/vendor/v1 \
> https://svn.doze.net/memleak/vendor/v2
>
> I'm using the Debian (sarge) svn package:
>
> svn, version 1.1.4 (r13838)
> compiled May 13 2005, 06:29:47
>
> Please let me know if you need any other information. Thanks.

Using the latest trunk, it doesn't climb higher than 26MB on my machine. The
patch should make it into the upcoming release (1.2.2).

-John

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 29 23:40:13 2005

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