[ http://issues.apache.org/jira/browse/MODPYTHON-60?page=all ]
Jim Gallacher resolved MODPYTHON-60:
------------------------------------
Fix Version: 3.2.0
3.3.0
Resolution: Fixed
Assign To: Jim Gallacher
> PythonOption directive causes memory leak
> -----------------------------------------
>
> Key: MODPYTHON-60
> URL: http://issues.apache.org/jira/browse/MODPYTHON-60
> Project: mod_python
> Type: Bug
> Components: core
> Versions: 3.1.4, 3.1.3, 3.2.0
> Environment: Linux
> Reporter: Jim Gallacher
> Assignee: Jim Gallacher
> Priority: Critical
> Fix For: 3.3.0, 3.2.0
>
> This was previously reported on the mod_python mailing list. See
> http://www.modpython.org/pipermail/mod_python/2004-April/015395.html
> A memory leak results when there is a PythonOption directive in the apache
> config file. Leak occurs when PythonOption is in either <VirtualHost> or
> <Directory> section.
> For each request, approx 25 bytes of memory is leaked per PythonOption
> directive.
> Methodolgy (using top to gauge memory usage, 100,000 requests per test case):
> def handler(req):
> req.content_type = 'text/plain'
> req.write('PythonOption test\n')
> return apache.OK
> 1. No PythonOption directives:
> 1.4 % MEM
> 2. 50 PythonOption directives:
> 11.3% MEM
> 3. 100 PythonOption directives:
> 25.4 % MEM
> I know 50 or 100 PythonOptions is not likely in a production system, but it
> clearly demonstrate the leak.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
