Hide Forgot
Description of problem: When checking out a big file one apache process grows larger and larger, until Linux OOM killer process invocation. My test environment is: Mem: 512M (virtual box vm) Checkout size: 2 files of 600M Httpd process memory consumption: >91% before OOM killer invocation Version-Release number of selected component (if applicable): Server side: subversion-1.6.11-7.el5_6.3 mod_dav_svn-1.6.11-7.el5_6.3 neon-0.25.5-10.el5_4.1 httpd-2.2.3-45.el5.centos.1 (with prefork MPM) Client side: subversion-1.6.11-7.el5_6.3 How reproducible: Making a >= 1.2G checkout on a 512M memory httpd/subversion server (tested with command line and tortoise clients) Steps to Reproduce: 1.check out a project from the Subversion repository svn co --username admin http://svn.tp3.codendi4.xrce.xerox.com/svnroot/tp3 2.create 2 600M files cd tp3/ dd if=/dev/urandom of=bigfile1 bs=6M count=100 dd if=/dev/urandom of=bigfile2 bs=6M count=100 3.commit them in the repository svn ci bigfile1 svn ci bigfile2 4.delete the project and check it out again cd ../ svn co --username admin http://svn.tp3.codendi4.xrce.xerox.com/svnroot/tp3 5.monitor httpd process on server side Actual results: One httpd process keeps growing until linux OOM killer invocation and check out is interrupted Expected results: Check out proceeding until completion (as it actually happens using svn co svn+ssh://giulio.codendi4.xrce.xerox.com/svnroot/tp3) Additional info: Apache virtual host configuration <Location /svnroot/tp3> DAV svn SVNPath /var/lib/codendi/svnroot/tp3 AuthzSVNAccessFile /var/lib/codendi/svnroot/tp3/.SVNAccessFile Require valid-user AuthType Basic AuthName "Subversion Authorization (Test Project 3)" PerlAccessHandler Apache::Authn::Codendi::access_handler PerlAuthenHandler Apache::Authn::Codendi::authen_handler CodendiDSN "DBI:mysql:codendi:localhost" CodendiDbUser "dbauthuser" CodendiDbPass "dbauth" CodendiGroupId "107" CodendiCacheCredsMax 10 SVNIndexXSLT '/svn/repos-web/view/repos.xsl' </Location> Prefork MPM configuration <IfModule prefork.c> StartServers 8 MinSpareServers 5 MaxSpareServers 20 ServerLimit 256 MaxClients 256 MaxRequestsPerChild 100 MaxMemFree 512 </IfModule>
O.S version is CentOS 5.6
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.