[rt-users] Help - memory leak problems

[Ruslan U. Zakirov]

douglas.borrie at eject.co.za wrote:
Look through all config not only VirtualHost section.

> This was my previous config
> 
> <VirtualHost host.domain.name>
>         ServerName host.domain.name
>         DocumentRoot /opt/rt3/share/html
>         AddDefaultCharset UTF-8
> 
>         PerlModule Apache::DBI
>         PerlRequire /opt/rt3/bin/webmux.pl
> 
>         <Location />
>                 SetHandler perl-script
>                 PerlHandler RT::Mason
>         </Location>
> </VirtualHost>
> 
> I changed it to this (is this what you meant by turning off Apache::DBI?)
> 
> <VirtualHost host.domain.name>
>         ServerName host.domain.name
>         DocumentRoot /opt/rt3/share/html
>         AddDefaultCharset UTF-8
> 
>         PerlRequire /opt/rt3/bin/webmux.pl
> 
>         <Location />
>                 SetHandler perl-script
>                 PerlHandler RT::Mason
>         </Location>
> </VirtualHost>
> 
> If that is what you meant, then yes the issue is still there.
> 
> 
> Quoting Jesse Vincent <jesse at bestpractical.com>:
> 
> 
>>Do you still see this issue if you turn off Apache::DBI?
>>
>>
>>On Fri, Oct 17, 2003 at 10:19:28AM +0200, douglas.borrie at eject.co.za wrote:
>>
>>>Hi all
>>> 
>>>I recently installed RT 3.0.4 (and later RT 3.0.6) using apache 1.3.28 and
>>>mod_perl 1.29 statically linked.
>>>I followed all the installation instructions and have installed it on a
>>
>>Solaris
>>
>>>2.6 as well as a Redhat Linux 9
>>>box but with the same problem occuring on both.
>>>The problem appears to be some sort of memory leak where memory is
>>
>>allocated but
>>
>>>is never released.
>>>The size of the httpd processes grow after every request.
>>>The end result is that all RAM is consumed and after a while all swap is
>>
>>also
>>
>>>exhausted.
>>> 
>>>Below are samples taken of the relevant processes (top output - sorted by
>>
>>memory
>>
>>>usage) while a dummy load is applied.
>>>The load is generated by multiple web clients with a URL similar to the
>>>following
>>>http://host.domain.name/index.html?HomeRefreshInterval=2 (Refresh the home
>>
>>page
>>
>>>every 2 seconds - too speed things up a bit)
>>> 
>>>As you'll see the size of the processes grow and eventually all memory is
>>
>>used.
>>
>>>The only thing that I have found to help is to set MaxRequestsPerChild=1
>>
>>in
>>
>>>apache config,
>>>but performance is really bad as after each request is handled that apache
>>
>>child
>>
>>>is killed and another
>>>is restarted in it's place. I also have to limit MinSpareServers and
>>>MaxSpareServers to about 4 with
>>>MaxClients also set to 4.
>>> 
>>>I have searched through the mailing list archives but I don't see anybody
>>
>>else
>>
>>>with
>>>the same problem (some are similar but I don't seem to find a solution)
>>> 
>>>I would really appreciate any help you could give me.
>>>