Project

General

Profile

Actions
Copy link

Bug #185

closed

3 important bugs to be fixed.

Added by Anonymous over 19 years ago. Updated about 1 year ago.

Status:
Fixed
Priority:
High
Category:
core
Target version:
-
ASK QUESTIONS IN Forums:
No

Description

Hi,
I tried lighttpd and I'd like to use it but there are 3 bugs that need to be fixed before that.

- keep-alive doesn't work with mod_proxy - the server is closing connection to clients and it shouldn't
  - there is a memory leak - at least on FreeBSD 4.8 using kqueue. In 6 hours the lighttpd grew from 2 MB to over 60 MB in size.
  - kill -HUP doesn't work. When HUP signal is received the lighttpg is growing in size fast and consumes a lot of CPU.

-- tgabi

Actions
Copy link
 #1

Updated by stbuehler over 16 years ago

  • Status changed from New to Fixed
  • Resolution set to worksforme

too old. (there is no memory leak, it gets reused)

Actions
Copy link
 #2

Updated by stbuehler over 16 years ago

  • Status changed from Fixed to Missing Feedback
Actions
Copy link
 #3

Updated by gstrauss about 1 year ago

  • Description updated (diff)
  • Status changed from Missing Feedback to Fixed
  • ASK QUESTIONS IN Forums set to No
  • mod_proxy works as designed and sends a single connection to the backend and then closes the request. In the future, there might be a feature added to configure backend connection reuse.
  • kill -HUP does not restart lighttpd. For historic reasons, HUP only causes lighttpd to reopen its logs. Therefore the memory issue reported is the same as the next point.
  • lighttpd did not leak memory, but before lighttpd 1.4.40 lighttpd might buffer very large responses fully in memory leading to a large memory footprint. This has been fixed since lighttpd 1.4.40 (released in 2016)
Actions
Copy link

Also available in: Atom