Bug 1623
Summary: | kill -HUP `cat /var/run/httpsd.pid` aggrevates memory leak | ||
---|---|---|---|
Product: | [Retired] Red Hat Secure Web Server | Reporter: | cdent |
Component: | mod_perl | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 2.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-01-13 04:46:11 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
cdent
1999-03-19 06:56:08 UTC
mod_perl 1.19 still has this memory leak. I am discussing things with the developers. I'm seeing major problems with busy servers without using mod_perl, too. My httpsd processes are growing to over 50 megs total size pretty quickly if they see significant load. The one test server I had with mod_perl included grew to over 150 megs without any load at all. Any progress on this? the concensus among mod_perl people seems to be to restart the server periodically in a cron job if you are experiencing memory leaks. While the problem may be fixed in a better way down the road, this is the current solution, and while sub-optimal, it works. |