| Nicolas Lehuen 2006-06-30, 7:12 am |
| Hi,
The subject of this thread is about mod_python 3.2.8, yet you report using
mod_python 3.1.3. Which version have you detected the memory leak in ? There
are a bunch of leaks that have been fixed since 3.1.3...
Regards,
Nicolas
2006/6/30, Harold Ship (JIRA) <jira@apache.org>:
>
> [
> http://issues.apache.org/jira/brows...action_12418577]
>
> Harold Ship commented on MODPYTHON-172:
> ---------------------------------------
>
> I've been able to reproduce the problem with "mod_python.publisher".
>
> Using:
> Windows 2000 Professional
> apache 2.0.54
> Python 2.3.5
> mod_python 3.1.3
>
> the following script:
> #foo.py
> def bar(req):
> a=req.form.getfirst('a')
> req.write('a=%s'%str(a))
> req.write('Ok')
>
> repeatedly sending requests to <addr>/foo/bar?a=b causes memory to rise
> continuously. removing the querystring does not. I used task manager to
> measure memory.
>
> I've also found that the following change to util.py corrects this
> behaviour:
>
> old util.py:
> parse_qs = _apache.parse_qs
> parse_qsl = _apache.parse_qsl
>
>
> workaround util.py:
> parse_qs = _apache.parse_qs
> #parse_qsl = _apache.parse_qsl
> from cgi import parse_qsl
>
>
> 2.0.55
> --------------------------------------------------------------------------
>
>
> described below.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> http://issues.apache.org/jira/secur...nistrators.jspa
> -
> For more information on JIRA, see:
> http://www.atlassian.com/software/jira
>
>
|