Max Bowsher wrote:
> Graham Dumpleton wrote:
>> Okay, found the source of the memory leak. The problem goes right back
>> to 3.1.4 which also has the problem when tested.
> ...
>> Now what do we do about 3.2.10? Given that this thing leaks really badly
>> when triggered shows that no one must be us
Here is further confirmation that it leaks like crazy for:
mod_python 3.2.10, Linux Ubuntu 6.06, Apache 2.0.55 (mpm-worker), Python
2.4.3
Jim
Graham Dumpleton wrote:
> I get it on Apache 2.0.59 as well. :-(
>
> I will thus be interested to see what others get, as appears to be an existing
> mod
Graham Dumpleton wrote:
> Okay, found the source of the memory leak. The problem goes right back
> to 3.1.4 which also has the problem when tested.
...
> Now what do we do about 3.2.10? Given that this thing leaks really badly
> when triggered shows that no one must be using multiple handler phases
Okay, found the source of the memory leak. The problem goes right back
to 3.1.4 which also has the problem when tested.
The problem code is in python_handler() in 'src/mod_python.c'.
Specifically
the code does:
if (!hle) {
/* create a handler list object from dynamically registere
The good news is that this isn't a problem introduced with mod_python
3.2.10
so doesn't necessarily have to stop that being released.
The bad news though is that is is also in mod_python 3.2.8, so it has
been
there for some time.
The question now is whether anyone else sees it on other plat
I get it on Apache 2.0.59 as well. :-(
I will thus be interested to see what others get, as appears to be an existing
mod_python issue.
BTW, this is with worker MPM.
Graham
Graham Dumpleton wrote ..
> I am using Apache 2.2.2 and when using mod_python in a certain way, I am
> seeing
> significan
