[ https://www.modsecurity.org/tracker/browse/MODSEC-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Breno Silva Pinto resolved MODSEC-106.
--------------------------------------
Resolution: Cannot Reproduce
> Memory usage grows high after some time (memory leak?)
> ------------------------------------------------------
>
> Key: MODSEC-106
> URL: https://www.modsecurity.org/tracker/browse/MODSEC-106
> Project: ModSecurity
> Issue Type: Bug
> Security Level: Normal
> Affects Versions: 2.5.9
> Environment: Apache/2.2.3
> CentOS release 5.3 (Final)
> 2.6.18-128.1.10.el5 #1 SMP Thu May 7 10:35:59 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Dawid Golunski
> Assignee: Breno Silva Pinto
> Priority: High
>
> I noticed that after 2 days of running modsecurity console (v2.5.9) on a pipe with apache memory used by the mlogc proccess
> grows very high. Here is a proccess entry from ps aux:
> USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
> root 25022 0.0 0.5 327072 46260 ? Sl Dec06 1:16 /usr/bin/mlogc /etc/mlogc.conf
> When I restart apache the memory usage is:
> root 31586 0.0 0.0 69960 2308 ? Sl 17:57 0:00 /usr/bin/mlogc /etc/mlogc.conf
> My guess is that there is a memory leak somewhere in the code.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|