> > I have a problem, apache is eating al my memory. It seems to allocate > the > > memory while I checkout or commit things. But then it don't > deallocate the > > memory after it is finish. Instead it just allocate more and more > until the > > memory is filled up. > > Only other known issue is to make sure you are not using mod_deflate > in conjunction with Subversion. This results in a known memory leak > when a Subversion client that does not support deflate is used. > Hi all,
I've just come across this issue myself after upgrading our Subversion server from Debian Etch (Apache 2.2.3) to Debian Lenny (Apache 2.2.9). Both servers were running subversion and the apache modules compiled from the 1.6.12 source. A client with a 1.5.x version of TortoiseSVN tried a fresh checkout of a large repository and the serving process ate about 30GB of RAM+Swap on the server in the space of less than 10 minutes. As it's only an internal server, we've just disabled mod_deflate and the problem has gone away. However, I'd like to understand a bit more about the issue, as mod_deflate is a default component and I can see this cropping up again in the future. I've (just about) followed the thread at [1] but it disappears into an old apache bug and I can't find anything else in apache's lists about it. I realise this isn't a subversion bug, but does anyone know if this has been addressed in apache? (Or have I missed some more recent discussion?) [1] http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2383415 Cheers, Terry.
