Bug #523

valgrind: possible memory leaks in lighttpd.

Added by Anonymous 1024 days ago. Updated 55 days ago.

Status:Invalid Start:
Priority:High Due date:
Assigned to:- % Done:

0%
Category:core
Target version:-
Pending:

 Resolution:

invalid
Patch available:

Description

I'm seeing a huge memory usage with lighttpd 1.4.10 under Linux and I tried valgrind http://valgrind.org to find out more on possible memory leaks. I don't know if valgrind is wrong, but it does report a fair amount of memory not deallocated.

If you would like to reproduce this, I recompiled lighty with -O0 and used:


# valgrind --show-reachable=yes --leak-check=yes /usr/sbin/lighttpd

Hope this helps.

History

03/04/2006 03:20 PM - jan

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

we check for leaks regularing and most of the shown leaks are static buffers in external libaries like openssl or dl.

10/10/2008 06:51 PM - stbuehler

  • Status changed from Fixed to Invalid

Also available in: Atom PDF