Project

General

Profile

Bug #1567

missing cleanup in fastcgi

Added by Anonymous over 11 years ago. Updated almost 11 years ago.

Status:
Invalid
Priority:
Urgent
Assignee:
-
Category:
mod_fastcgi
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Missing in 1.5.x:

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

History

#1

Updated by Anonymous over 11 years ago

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

-- Lfe

#2

Updated by stbuehler over 11 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

#3

Updated by Anonymous over 11 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

#4

Updated by Anonymous over 11 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

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

"Localhost".

Quite useless.

#5

Updated by Anonymous over 11 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.

#6

Updated by stbuehler over 11 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.

#7

Updated by Anonymous over 11 years ago

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

#8

Updated by Anonymous over 11 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

#9

Updated by stbuehler over 11 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).

#10

Updated by stbuehler almost 11 years ago

  • Status changed from Fixed to Invalid

Also available in: Atom