[
https://issues.apache.org/jira/browse/MODPYTHON-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768559#action_12768559
]
Graham Dumpleton commented on MODPYTHON-235:
--------------------------------------------
No plans to fix it. No plans for any work to be done on mod_python by anyone.
The fix as described also isn't sufficient anyway as Python itself leaks memory
even when Py_Initialize() is called. For mod_python 3.X that is by design. For
Python 2.X, which is all mod_python supports anyway, not clear if the memory
leaks in Python are by design or unintended. Could perhaps be a mix of both.
If you are using mod_python purely for purposes of hosting a Python web
application which also has a WSGI interface, you should consider moving to
mod_wsgi. The mod_wsgi package ensure that Py_Finalize() is called and so that
aspect of leak doesn't exist. There is still the issue with Python itself
leaking, but in mod_wsgi 3.X that is avoided by delaying initialisation of
Python until after processes fork.
Do note that although you can use mod_python and mod_wsgi in process together,
you will still be subject to memory leaks because mod_python behaviour takes
precedence and so it will still leak. Thus, only use mod_wsgi alone and don't
use mod_python at the same time.
> Memory leaks in main Apache process when doing 'restart' or 'graceful'.
> -----------------------------------------------------------------------
>
> Key: MODPYTHON-235
> URL: https://issues.apache.org/jira/browse/MODPYTHON-235
> Project: mod_python
> Issue Type: Bug
> Components: core
> Affects Versions: 3.3.1
> Reporter: Graham Dumpleton
>
> As raised in thread:
> http://www.modpython.org/pipermail/mod_python/2007-June/023926.html
> it looks like mod_python exhibits memory leaks in the main Apache process
> when a 'restart' or 'graceful' is done. Ie., when only child process are
> killed off and restarted rather than whole Apache being stopped.
> The poster though seems to be of opinion that it only happens when certain
> auth modules are loaded, which makes the behaviour somewhat odd if true. One
> would expect it simply to always leak rather than being dependent on the
> other modules existing.
> As it stands, the whole mod_python initialisation really needs to be done
> over because of issues such as MODPYTHON-195. If done it may resolve this
> problem.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
