The contract type is `' with a response time of 3 business hours.
A first analysis should be sent before: Wed Apr 16 15:00:01 PDT 1997
>Number: 406
>Category: general
>Synopsis: Severe memory leak -- possibly due to SIGSEGV
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: apache (Apache HTTP Project)
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Wed Apr 16 11:40:01 1997
>Originator: [EMAIL PROTECTED]
>Organization:
apache
>Release: Apache/1.2b8
>Environment:
FreeBSD 2.2.1-RELEASE #0: Sun Apr 13
Server version Apache/1.2b8 PHP/FI-2.0b11.
(256MB RAM, httpd.h:#define HARD_SERVER_LIMIT 500)
>Description:
procs memory page faults cpu
r b w avm fre flt re pi po fr sr w0 in sy cs us sy id
2 1 0 122464 87344 19 0 0 0 19 0 1 762 1970 1236 27 17 56
grep -i SEGV error_log | wc -l
632 <-- 55 per hour!
** Continual segment violations, to the tune of almost 1 per minute,
are slowly eating away at server memory resources. Free memory gets
depleted until a server reboot is necessary. Memory not being freed.
[Mon Apr 14 09:49:28 1997] httpd: caught SIGSEGV,
attempting to dump core in /usr/local/etc/httpd
[Mon Apr 14 09:50:07 1997] httpd: caught SIGSEGV,
attempting to dump core in /usr/local/etc/httpd
>How-To-Repeat:
Just run Apache/1.2b8, and do "vmstat" over a period of days.
On a heavily-loaded site, you will soon find that memory is not
being reclaimed, and the grim reaper soon visits. I can give
you access to my site, if need be.
>Fix:
A salary for the developers might be a nice start.
%0
>Audit-Trail:
>Unformatted:
