Excess memory usage when calling read()/readline() on wsgi.input with no arguments.

jvandal / modwsgi

Automatically exported from code.google.com/p/modwsgi

0 stars 0 forks source link

Excess memory usage when calling read()/readline() on wsgi.input with no arguments. #126

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

When calling read() or readline() with no arguments on wsgi.input then 
excessive transient memory 
usage can occur.

Note that calling read() with no arguments is actually a violation of WSGI 
specification and a WSGI 
compliant program shouldn't be calling it.

The excessive memory usage will be greater as the size of request input grows.

Original issue reported on code.google.com by Graham.Dumpleton@gmail.com on 27 Jan 2009 at 2:21

GoogleCodeExporter commented 8 years ago

Fixed in revision 1162 of trunk for 3.0.

Original comment by Graham.Dumpleton@gmail.com on 27 Jan 2009 at 2:23

Changed title: Excess memory usage when calling read()/readline() on wsgi.input with no arguments.
Changed state: Started
Added labels: Milestone-Release3.0

GoogleCodeExporter commented 8 years ago

Backported to 2.X branch for 2.4 at revision 1219.

Original comment by Graham.Dumpleton@gmail.com on 7 Mar 2009 at 1:01

Added labels: Milestone-Release2.4
Removed labels: Milestone-Release3.0

GoogleCodeExporter commented 8 years ago

Version 2.4 of mod_wsgi now released.

Original comment by Graham.Dumpleton@gmail.com on 11 Apr 2009 at 10:25

Changed state: Fixed