Core +1 from me. I will take care of the signing, etc, some time tomorrow.
P.S. In order for you to be able to sign you need to meet in person
someone (or probably more than one person) from ASF. ApacheCon is the best
place, and members do not have to pay the conference fee (at least I think
[ http://issues.apache.org/jira/browse/MODPYTHON-181?page=all ]
Graham Dumpleton resolved MODPYTHON-181.
Fix Version/s: 3.3
Resolution: Fixed
> Memory leak when using handlers in multiple phases at same time.
>
Nicolas Lehuen wrote ..
> Note that the problem with Apache 2.2 on Windows XP SP2 seems to have
> disappeared, though I can't see how this is possible, unless Graham fixed
> something :).
>
> The problem was more probably due to an Apache 2.2 setup glitch.
Not necessarily a glitch. The whole prob
Note that the problem with Apache 2.2 on Windows XP SP2 seems to have disappeared, though I can't see how this is possible, unless Graham fixed something :).The problem was more probably due to an Apache 2.2 setup glitch.
Regards,Nicolas2006/7/31, Jim Gallacher <[EMAIL PROTECTED]>:
We decided to fi
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
We decided to fix the memory leak in parse_qsl and move on to 3.2.10,
which has been tested and currently has +3 core votes. All we need now
is the official release. One of these days I'll sort out my GPG keys so
I can sign these things myself but in the mean time we'll need your
help, Grisha.
Mai
[ http://issues.apache.org/jira/browse/MODPYTHON-181?page=all ]
Work on MODPYTHON-181 started by Graham Dumpleton.
> Memory leak when using handlers in multiple phases at same time.
>
>
> Key: MODPYTHON-181
>
Memory leak when using handlers in multiple phases at same time.
Key: MODPYTHON-181
URL: http://issues.apache.org/jira/browse/MODPYTHON-181
Project: mod_python
Issue Type: Bug
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
12 matches
Mail list logo
