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

Progress on issue 1964 (mem leak on commit)

From: Erik Huelsmann <e.huelsmann_at_gmx.net>
Date: 2004-09-06 22:38:57 CEST

From what I just added to the issue:

Memory usage jumps from virtually none to 176M on my machine at the call to
svn_wc_adm_open2() in svn_client_commit (commit.c:1176 in r10813).

After that, memory usage climbs up steadily. This can be explained by the
fact that before the commit a list of committable targets is collected *in
memory*. During the commit, a list of temporary files is collected in memory

I think this might not be a leak, just poor design: we read the entries
into memory recursively. From what I have seen so far, most of our
libraries are quite good at doing streamy processing. libsvn_client and
libsvn_wc don't seem to be among those libraries. From what I've seen
making them streamy (or at least some operations) might be the only solution
to limiting memory use on commit (and add and others?).

Ben (Collins-Sussman), I'm out of time to look into this now, but I hope the
answer is satisfying.



Supergünstige DSL-Tarife + WLAN-Router für 0,- EUR*
Jetzt zu GMX wechseln und sparen http://www.gmx.net/de/go/dsl
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 6 22:39:21 2004

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.