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

mem leak?

From: Neels Janosch Hofmeyr <neels_at_elego.de>
Date: Fri, 30 Oct 2009 13:46:04 +0100


here's a report from crazy_imp on #svn:

With 1.6.6, a checkout of freebsd was interrupted by a network reconnect
(takes longer than a day o_O). After that, `svn cleanup' takes some hours to
complete, and after that, `svn update' grows to about 3 gig memory usage.

Don't know what to make of it, maybe someone else would like to investigate.
Some chat snippets...

<crazy_imp> svn, Version 1.6.6 (r40053)
<crazy_imp> neels: all i've done is: svn co svn://svn.freebsd.org/base/
freebsd - due reconnects, i need to run svn cleanup and svn up again.

<neels> so your checkout was interrupted, and you had to cleanup, then you
updated to try and finish the checkout. right?
<crazy_imp> yes

<crazy_imp> asked yesterday why svn does not reconnect to the server and
keeps on going after a reconnect, nobody answered the question (think it
should be possible, the client still knows it's state and which stuff he
needs to fetch)

<borg-queen> crazy_imp: are you really sure you want to checkout the whole
<crazy_imp> borg-queen: yes :)
<borg-queen> crazy_imp: then maybe a checkout "--depth immediates" and
updates of individual subdirs may work better

(etc., 2009-10-30 at about 13:00 CET)



Received on 2009-10-30 13:47:26 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.