Bug #1567
closedmissing cleanup in fastcgi
Description
"missing cleanup in fastcgi"
it's still there and it still causes to crash my server if i don't restart lighttpd every 15 minutes... this bug has been reported before...
Updated by Anonymous almost 17 years ago
Perhaps forum thread http://forum.lighttpd.net/topic/1321 solves your issue?
-- Lfe
Updated by stbuehler almost 17 years ago
- Status changed from New to Fixed
- Resolution set to invalid
Version 1.4.13? How do you think bugs get fixed if you do not update?
Duplicate #910, Fixed in r1720
Updated by Anonymous almost 17 years ago
Replying to stbuehler:
Version 1.4.13? How do you think bugs get fixed if you do not update?
Duplicate #910, Fixed in r1720
That's what I told the maintainers of the stable(!) debian package, too.
http://packages.debian.org/lighttpd
Updated by Anonymous almost 17 years ago
Updated by Anonymous almost 17 years ago
Replying to Lfe:
Perhaps forum thread http://forum.lighttpd.net/topic/1321 solves your issue?
No. He says his problem is solved. And the explanation how he solved it is a single word.
"Localhost".
Quite useless.
Updated by stbuehler almost 17 years ago
The debian bug was http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=400167, and it says it got fixed in 1.4.13-7 by applying the fix from #910.
The remaining problem is: that version is not in stable.
Updated by Anonymous almost 17 years ago
I'm using 1.4.13-10 from debian backports now. It works fine.
Updated by Anonymous almost 17 years ago
nah... 1.4.13-10 from debian backports doesn't work either... the message in the error.log is gone.. but it keeps allocating memory without freeing it... :C
Updated by stbuehler almost 17 years ago
Just don't send files with fastcgi and use x-sendfile instead - lighty does not free temporary buffers (but reuses them, so no real memleak).
Also available in: Atom