Bug #1265
closedSSL + file upload = lots of memory
Description
I'm using lighttpd (1.4.15) in an embedded device, and attempting to upload a file (~6MB). Without SSL enabled, lighttpd doesn't use much more than 6-7MB (lighttpd process grows by <1MB, ~6MB are written to /tmp). With SSL enabled, lighttpd's memory usage quickly jumps to over 26MB (lighttpd process grows to 20+MB, ~6MB are written to /tmp), exhausting all available memory and bringing the device to a grinding halt.
I also noticed that the <1MB of extra size on a non-SSL upload goes away once the upload is complete; in contrast, if I upload a smaller file (900kB) via SSL, the process size grows by ~7MB and stays that large, even after the connection is closed. However, uploading a similarly-sized file again does not cause it to grow any larger, i.e. the memory doesn't seem to be permanently leaked.
I found this ticket:
http://trac.lighttpd.net/trac/ticket/881
which sounds somewhat similar, but no additional information was ever posted about a potential cause. Any ideas? Thanks!
Files
Updated by stbuehler almost 17 years ago
- Status changed from New to Fixed
- Resolution set to wontfix
Updated by gstrauss almost 9 years ago
- Related to Bug #881: memory usage when ssl.engine used and large data uploaded through CGI added
Updated by gstrauss almost 9 years ago
- Related to Bug #949: fastcgi, cgi, flush, php5 problem. added
Updated by gstrauss almost 9 years ago
- Description updated (diff)
- Status changed from Wontfix to Patch Pending
- Target version changed from 1.5.0 to 1.4.40
Updated by gstrauss almost 9 years ago
- Status changed from Patch Pending to Fixed
- % Done changed from 0 to 100
Also available in: Atom