quetz-mod_python-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Graham Dumpleton <grah...@dscpl.com.au>
Subject Fwd: MODPYTHON-195
Date Sat, 04 Nov 2006 02:17:50 GMT
Forwarding this back to the list merely so it goes in mailing list  
archive.
This relates to the leaking handles on Win32 platform.

Begin forwarded message:

> From: "Jeff Robbins" <jeffr@livedata.com>
> Date: 4 November 2006 12:34:19 PM
> To: "Graham Dumpleton" <grahamd@dscpl.com.au>
> Subject: MODPYTHON-195
>
> Graham,
>
> I haven't had any new ideas about this problem.  It is clear that  
> on Windows, mod_python is initialized both in a parent process and  
> more usefully in the child process that spins up the threads that  
> service client requests.  The parent process is long-lived and the  
> standard hack to wait for the second call to the  
> ap_hook_post_config is useless because each "restart" of apache is  
> yet another call (third, fourth, fifth, etc...) and each time  
> there's a leak of one handle.
>
>
> The fix I tested seems reasonable.  I know it is dependent on  
> mpm_winnt.c, but, after all, that file is the file responsible for  
> the dual process architecture on windows to begin with.  And the  
> fix has an #ifdef win32 so it won't hurt linux users.
>
> I'd like you to consider folding it in.  I think it is better than  
> having a leak (along with spurious python initialization) on windows.
>
> Thanks,
>
> Jeff

Mime
View raw message