You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mod_python-dev@quetz.apache.org by "Graham Dumpleton (JIRA)" <ji...@apache.org> on 2007/05/01 12:51:15 UTC
[jira] Closed: (MODPYTHON-194) Memory leak due to not clearing
thread state object before deletion.
[ https://issues.apache.org/jira/browse/MODPYTHON-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Graham Dumpleton closed MODPYTHON-194.
--------------------------------------
> Memory leak due to not clearing thread state object before deletion.
> --------------------------------------------------------------------
>
> Key: MODPYTHON-194
> URL: https://issues.apache.org/jira/browse/MODPYTHON-194
> Project: mod_python
> Issue Type: Bug
> Components: core
> Affects Versions: 3.2.10
> Reporter: Graham Dumpleton
> Assigned To: Graham Dumpleton
> Fix For: 3.3
>
>
> Jeff Robbins reported a potential memory leak in mod_python as a result of PyThreadState_Clear() not being called prior to PyThreadState_Delete. See:
> http://mail-archives.apache.org/mod_mbox/httpd-python-dev/200610.mbox/%3c3308644A-9EE5-48BA-845F-EF3F43BB68FF@dscpl.com.au%3e
> Problem looks to be valid, but as per followup:
> http://mail-archives.apache.org/mod_mbox/httpd-python-dev/200610.mbox/%3cA62494E5-D8FE-458B-9700-EEEC1EB11FE8@dscpl.com.au%3e
> the location of the PyThreadState_Clear() call would need to be moved to before the lock is released.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.