[ http://issues.apache.org/jira/brows...ON-195?page=all ]

Graham Dumpleton resolved MODPYTHON-195.
----------------------------------------

Resolution: Fixed

Haven't been able to validate this first hand, but have accepted the followi
ng change in python_init() to stop Win32 parent process performing global mu
tex and Python initialisation.

#ifdef WIN32
/* No need to run python_init() in Win32 parent processes as
* the lack of fork on Win32 means we get no benefit as far as
* inheriting a preinitialized Python interpreter. Further,
* upon a restart on Win32 platform the python_init() function
* will be called again in the parent process but without some
* resources allocated by the previous call having being
* released properly, resulting in memory and Win32 resource
* leaks.
*/
if (!getenv("AP_PARENT_PID"))
return OK;
#endif /* WIN32 */


See MODPYTHON-195 thread at:

http://mail-archives.apache.org/mod...611.mbox/thread

starting with:

http://mail-archives.apache.org/mod...dscpl.com.au%3e





> Possible leaking of Win32 event handles when Apache restarted.
> --------------------------------------------------------------
>
>                 Key: MODPYTHON-195
>                 URL: http://issues.apache.org/jira/browse/MODPYTHON-195
>             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 Robins in:
>   http://mail-archives.apache.org/mod...dscpl.com.au%3e
> indicates a belief that when an Apache restart is performed on Windows that there 
are a number of Win32 event handles leaked. His belief is that this seems to be link
ed to mod_python.

[ Post a follow-up to this message ]