Apache Mod-Python - Closed: (MODPYTHON-194) Memory leak due to not clearing

This is Interesting: Free IT Magazines  
Home > Archive > Apache Mod-Python > May 2007 > Closed: (MODPYTHON-194) Memory leak due to not clearing





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Closed: (MODPYTHON-194) Memory leak due to not clearing
Graham Dumpleton (JIRA)

2007-05-01, 7:12 am


[ https://issues.apache.org/jira/brow...ls: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...dscpl.com.au%3e
> Problem looks to be valid, but as per followup:
> http://mail-archives.apache.org/mod...dscpl.com.au%3e
> the location of the PyThreadState_Clear() call would need to be moved to before the lock is released.


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com