Michael <ectosphenoid-svn@yahoo.com> writes:
> Here is a better example of the memory leak.
>
> $ ~/tmp> dir
> $ ~/tmp> co svn://localhost/test
> Checked out revision 0.
> $ cd test
> $ ~/tmp/test> for d1 in a b c d e f g h i j k l m n o p q r;
> > do
> > mkdir $d1
> > cd $d1
> > for d2 in a b c d e f g h i j k l m n o p q r;
> > do
> > mkdir $d2
> > cd $d2
> > for f1 in 0 1 2 3 4 5 6 7 8 9;
> > do
> > for f2 in 0 1 2 3 4 5 6 7 8 9;
> > do
> > for f3 in 0 1 2 3 4 5 6 7 8 9;
> > do
> > dd if=/dev/urandom of=$f1$f2$f3 bs=1024 count=1 > /dev/null 2>&1
> > done
> > done
> > done
> > cd ..
> > done
> > cd ..
> > done
> $ ~/tmp/test> svn add -q *
> $ ~/tmp/test> ulimit -c 0
> $ ~/tmp/test> ulimit -d 131072
> $ ~/tmp/test> svn commit -q -m "add 324,000 1KB files to bdb repo"
> Abort trap
> $ ~/tmp/test> svn cleanup
> Abort trap
>
> The svn add command also leaks but not nearly as much as the commit and
> cleanup. Both the commit and cleanup failed within seconds as the
> memory quickly climbed to the 128MB limit.
Just checking: these leaks are all on the client side, right?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 21 17:55:47 2004