Project

General

Profile

Actions
Copy link

Bug #1770

closed

memory leak : mod_proxy_backend_fastcgi

Added by Anonymous about 16 years ago. Updated 11 months ago.

Status:
Obsolete
Priority:
Normal
Category:
mod_proxy_backend_fastcgi
Target version:
1.5.0
ASK QUESTIONS IN Forums:
No

Description

Hi guys,
it seems that mod_proxy_backend_fastcgi of lighttpd-1.5.0-r1992 has a bug of memory leak.
the memory used by lighttpd is increesing by 2M bytes every minute and finally leed to a problem that the service terminated.
there are some messages of the errorlog below.

mod_proxy_backend_fastcgi.c.484: (trace) 0 / 0 -> 0
mod_proxy_backend_fastcgi.c.487: (error) looks like the fastcgi-backend (/xxx/) terminated before it sent a FIN packet
mod_proxy_backend_fastcgi.c.484: (trace) 0 / 0 -> 0
mod_proxy_backend_fastcgi.c.487: (error) looks like the fastcgi-backend (/xxx/) terminated before it sent
a FIN packet
mod_proxy_backend_fastcgi.c.484: (trace) 0 / 0 -> 0
mod_proxy_backend_fastcgi.c.487: (error) looks like the fastcgi-backend (/xxx/) terminated before it sent
a FIN packet

-- marchslen

Actions
Copy link
 #1

Updated by Anonymous about 16 years ago

try with the new snapshot.. Do you get the memleak with that too?
http://blog.lighttpd.net/articles/2008/08/20/new-prereleases-1-4-20-r2294-and-1-5-r2294

Actions
Copy link
 #2

Updated by nitrox about 16 years ago

  • Status changed from New to Need Feedback
  • Priority changed from Urgent to Normal
  • Patch available set to No
Actions
Copy link
 #3

Updated by stbuehler about 16 years ago

  • Status changed from Need Feedback to Missing Feedback
Actions
Copy link
 #4

Updated by gstrauss 11 months ago

  • Status changed from Missing Feedback to Obsolete
  • ASK QUESTIONS IN Forums set to No

lighttpd 1.5.x branch has been abandoned.

lighttpd 1.4.x branch is now far more advanced and continues to be maintained.

Actions
Copy link

Also available in: Atom