Your message dated Wed, 21 Feb 2018 00:30:25 -0500 with message-id <[email protected]> and subject line Re: Bug#647694: subversion: Memory leak in large repositories has caused the Debian Bug report #647694, regarding subversion: Memory leak in large repositories to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 647694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647694 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: subversion Version: 1.6.12dfsg-6 Severity: normal Executing svn cleanup with very large repository will end up using all available memory. This takes approximately few hours if I execute it in here: http://plugins.svn.wordpress.org/ Actual output from the svn-binary looks like: svn: REPORT of '/!svn/vcc/default': Could not read response body: connection was closed by server (http://plugins.svn.wordpress.org) Killed dmesg: <kernel info of memory. useless to put to this bug-report?> [5487380.861645] Out of memory: kill process 31248 (bash) score 349047 or a child [5487380.861649] Killed process 31310 (svn) I also tried this in server with over 100G of ram and still got the same situation. I am really sorry, but I don't know how to verify, which part of the code is taking all the memory or how to give you more details about this problem. If you want I can run spesific commands. I am not the owner of that repository, but I think it can be used in testing as long as you don't generate too much traffic there. Bugs, which could be similar issues: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=409054 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=280377 -- System Information: Debian Release: 6.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages subversion depends on: ii libapr1 1.4.2-6+squeeze3 The Apache Portable Runtime Librar ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libsasl2-2 2.1.23.dfsg1-7 Cyrus SASL - authentication abstra ii libsvn1 1.6.12dfsg-6 Shared libraries used by Subversio subversion recommends no packages. Versions of packages subversion suggests: pn db4.8-util <none> (no description available) ii patch 2.6-2 Apply a diff file to an original pn subversion-tools <none> (no description available) -- no debconf information
--- End Message ---
--- Begin Message ---Version: 1.9.3-1 On Sat, Nov 05, 2011 at 12:18:47PM +0200, Henri Salo wrote: > Executing svn cleanup with very large repository will end up using all > available memory. This takes approximately few hours if I execute it > in here: This looks like it was fixed in 1.9.3-1: * cleanup: avoid unneeded memory growth during pristine cleanup (r1706241) Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--- End Message ---
