[ http://issues.apache.org/jira/browse/MODPYTHON-194?page=all ]
Graham Dumpleton resolved MODPYTHON-194.
Resolution: Fixed
> Memory leak due to not clearing thread state object before deletion.
> --
[ http://issues.apache.org/jira/browse/MODPYTHON-194?page=all ]
Work on MODPYTHON-194 started by Graham Dumpleton.
> Memory leak due to not clearing thread state object before deletion.
>
>
> Key: MODPYTHON-
Rereading Trac code, the req.args in constructor is still an issue as
what
the code is actually doing is prevent util.FieldStorage processing
req.args
and for it to do it itself, only adding args where they aren't also
defined in
POST body.
The only way to provide a fiddle for this would be
[ http://issues.apache.org/jira/browse/MODPYTHON-186?page=all ]
Graham Dumpleton updated MODPYTHON-186:
---
Component/s: core
Fix Version/s: (was: 3.3)
(was: 3.2.x)
Defer fixing of this issue until have someone with th
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
[
http://issues.apache.org/jira/browse/MODPYTHON-127?page=comments#action_12443889
]
Jim Gallacher commented on MODPYTHON-127:
-
We need to make sure we address this in the unittests as well. Should we have
tests for the additional optio
Jim Gallacher wrote:
Graham Dumpleton wrote:
Jim Gallacher wrote ..
Although there is no JIRA issue for it, I'd like to see us do a quick
code cleanup. I see lots of complier warnings about unused variables and
it would be nice to excise the offending bits of code. I figure we are
more likely
