[mod_python] mod_python + mod_authz_host w/o mod_auth_digest causes ~1Mb leak per apache graceful restart

Graham Dumpleton graham.dumpleton at gmail.com
Thu Jun 28 20:15:48 EDT 2007

On 29/06/07, Graham Dumpleton <graham.dumpleton at gmail.com> wrote:
> On 29/06/07, Aseem Mohanty <aseem at metaweb.com> wrote:
> > They sure look like good candidates, so should I be looking at mod_wsgi in
> > daemon mode (we are serving WSGI apps via an adapter). The reason I ask is that
> > we need the graceful restarts and cannot really do without it for now.
> Maybe not. When I look at it, mod_wsgi is also leaking on 'graceful'
> and 'restart' as well. If these leaks are from Python itself not
> cleaning things up properly, not sure what I am going to do. Unlike
> mod_python I actually Py_Finalize() the interpreter in the main
> process so that everything is properly reset back to a clean slate, so
> I may actually be more susceptible to it than mod_python.
> I'll investigate the mod_wsgi problem and maybe that will throw some
> light on why mod_python also has problems.

Its okay to try mod_wsgi now if you want to see whether you get memory
leaks there as well. Just make sure you update from repository if you
already had it checked out. Obviously, don't load mod_python at the
same time.

The change I made in mod_wsgi was to comment out trigger for recycling
Python interpreter in main Apache process. This was only being done
for Apache 2.X and not Apache 1.3, so I know not doing it doesn't
cause a problem. I do still see very minor leaks, but the same ones I
get without mod_wsgi.

I'll try now and see what happens with mod_wsgi when I add the auth
modules you are talking about. If that is okay with mod_wsgi, can try
with mod_python and see if I can work out what the differences are.


More information about the Mod_python mailing list