[
https://issues.apache.org/jira/browse/MODPYTHON-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659530#action_12659530
]
Graham Dumpleton commented on MODPYTHON-235:
--------------------------------------------
These memory leaks are due to mod_python not calling Py_Finalize() call on
active Python interpreter instance. Result being that memory isn't released.
After restart Py_Initialize() is called again with memory being allocated
again. Thus see an incremental memory leak on every restart.
Code needs to register a cleanup callback on appropriate memory pool and
destroy interpreter properly prior to internal restart.
> 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.
