Greg Stein <gst...@gmail.com> writes: > I think the memory usage might actually be our test harness attempting > to read all of the (stderr) output into memory. Thousands and > thousands of lines that read: > > svn(56985,0xa0634720) malloc: *** error for object 0x817a00: double free > *** set a breakpoint in malloc_error_break to debug > > So maybe svn isn't consuming memory, but is simply generating a > hojillion of these error lines. I forced an abort/coredump, and found > this stack: > > #0 0x952e329a in write$NOCANCEL$UNIX2003 () > #1 0x9538f3ce in malloc_destroy_zone () > #2 0x9538e8e3 in malloc_zone_print_ptr_info () > #3 0x9538e943 in malloc_printf () > #4 0x9538941a in scandir$INODE64 () > #5 0x952b3523 in malloc_zone_free () > #6 0x952b338d in free () > #7 0x004d230c in apr_allocator_destroy (allocator=0x502010) at > memory/unix/apr_pools.c:134 > #8 0x000101b5 in main (argc=11, argv=0xbffff0ac) at > subversion/svn/main.c:2288
I don't see it on Linux (Debian stable) and I've run merge_tests 4 with the svn client running under valgrind. -- Philip
