On Tue, Aug 12, 2008 at 02:22:27PM -0400, Vincent Rivellino wrote:
> PS: Please reply-all, as I am not subscribed to the dev list.
Feel free to also set a proper Mail-Followup-To: header to simplify
replying for us :-)
> ---------------------------- Original Message ----------------------------
> Subject: memory problems w/ mod_dav_svn?
> From: "Vincent Rivellino" <vince_at_cuz.cx>
> Date: Mon, August 4, 2008 12:16
> To: users_at_subversion.tigris.org
> --------------------------------------------------------------------------
>
> Has anyone run into memory problems using mod_dav_svn w/ rather large
> repositories?
>
> I recently migrated our repositories to 1.5.1 and moved them from svn+ssh
> to mod_dav_svn via https.
> Can anyone offer any insight?
I'm not sure but the following may work:
Compile subversion from source containing debug information. I use:
./autogen.sh
./configure CXXFLAGS="-O0 -g" --enable-maintainer-mode --enable-debug
I assume mod_dav_svn is directly started from apache, right? In this
case please start apache manually with valgrind, which is a memory
checker
valgrind --leak-check=full --show-reachable=yes --trace-children=yes apache --log-file=log.file
Please note that valgrind makes apache slower by at least factor 10.
Nevertheless checking out a very small part of the repository should
probably show the problem.
I assume that the log file log.file.<pid> will be very very large.
Either make this file somewhere available or extract the first
Subversion related problems and send it to this list.
PS: IIRC someone mentioned that if valgrind will be used also the apr
library which is a dependency of subversion should be compiled with
debug information. I'm not sure about this.
Jens
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-08-13 10:50:47 CEST