Lighttpd

Perhaps forum thread http://forum.lighttpd.net/topic/1321 solves your issue?

-- Lfe

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

Replying to stbuehler:

Version 1.4.13? How do you think bugs get fixed if you do not update?

Duplicate #910, Fixed in r1720

No. He says his problem is solved. And the explanation how he solved it is a single word.

"Localhost".

Quite useless.

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.

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.

I'm using 1.4.13-10 from debian backports now. It works fine.

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

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).