Re: subversion 1.3.1 + apr 0.9.7 = memory leak?

"Garrett Rooney" <rooneg@electricjellyfish.net> writes:

> On 5/3/06, David Young <dyoung@pobox.com> wrote:
[...]
> > When I run commands such as 'svn co' and 'svn status -u' on the
> > repository, they take several minutes to run (i.e., too long), and svn's
> > memory usage climbs to 150MB, which seems unusually high. This is not
[...]
> Operations on large working copies (including checkout and status)
> will use amounts of memory proportional to its size, due to the
> caching of information about the entries in each directory.

Hmm. Only the entries for the directory currently being scanned
and all its parents need be in memory at once. There should be a
subpool for each directory, i would think. If it's growing
without bound, it sounds to me like *all* entries are staying in
memory. In other words, given

wc
wc/bin
wc/bin/ls
wc/bin/sh

wc/bin/ls entries should be in a pool that is freed before moving
on to wc/bin/sh.

> either that or you get unacceptable speed hits from parsing the
> entries file multiple times.

Once svn is finished printing status for wc/bin/ls, it will never
need those entries again.

-- 
Eric Gillespie <*> epg@pretzelnet.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org