Issue #1899 (svndumpfilter single-file-change scalability): Investigating
From: Shlomi Fish <shlomif_at_iglu.org.il>
Date: 2004-06-25 20:20:25 CEST
I took some time to investigate issue #1899:
http://subversion.tigris.org/issues/show_bug.cgi?id=1899
The reporter reported that if a large file was committed wholly at one commit,
After I ran the test script I provided in the issue, I do a:
(ulimit -v 100000 ; gdb --command=cmds.gdb svndumpfilter)
Where cmds.gdb is:
<<<
After I do a "c", the SIGABRT originates from:
<<<
Which is:
SVN_ERR (svn_stream_write (text_stream, buffer, &wlen));
The function reads the entire buffer from the file and writes it chunk by
Now text_stream according to my analysis eventually points to
<<<
So it just stores everything in memory.
So this is not in fact a memory leak, just a design decision that causes the
Regards,
Shlomi Fish
-- --------------------------------------------------------------------- Shlomi Fish shlomif@iglu.org.il Homepage: http://shlomif.il.eu.org/ Knuth is not God! It took him two days to build the Roman Empire. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org For additional commands, e-mail: dev-help@subversion.tigris.orgReceived on Fri Jun 25 20:17:19 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.