[syslog-ng] [Bug 150] Possible memory leak for TLS connections

bugzilla at bugzilla.balabit.com bugzilla at bugzilla.balabit.com
Fri Dec 2 07:03:11 CET 2011


https://bugzilla.balabit.com/show_bug.cgi?id=150





--- Comment #2 from Eric Lindvall <eric at sevenscale.com>  2011-12-02 07:03:09 ---
My basic testing has shown that this patch fixes the leak:

https://github.com/eric/syslog-ng-3.3/compare/free-tls-context.patch

I haven't been able to figure out if this entry from valgrind is related to a legitimate leak or just cleanup that doesn't happen on shutdown:

==5415== 6,349,488 bytes in 358 blocks are possibly lost in loss record 1,016 of 1,016
==5415==    at 0x4C25E46: malloc (vg_replace_malloc.c:195)
==5415==    by 0x7BA585D: CRYPTO_malloc (in /lib64/libcrypto.so.1.0.0e)
==5415==    by 0x7914A52: ssl3_setup_read_buffer (in /usr/lib64/libssl.so.1.0.0e)
==5415==    by 0x7914BA8: ssl3_setup_buffers (in /usr/lib64/libssl.so.1.0.0e)
==5415==    by 0x79151F4: ssl23_get_client_hello (in /usr/lib64/libssl.so.1.0.0e)
==5415==    by 0x7915602: ssl23_accept (in /usr/lib64/libssl.so.1.0.0e)
==5415==    by 0x7916790: ssl23_read (in /usr/lib64/libssl.so.1.0.0e)
==5415==    by 0x76EB111: log_transport_tls_read_method (tlstransport.c:56)
==5415==    by 0x50B58CC: log_proto_buffered_server_read_data (logtransport.h:74)
==5415==    by 0x50B6E79: log_proto_buffered_server_fetch (logproto.c:1115)
==5415==    by 0x50BA2E0: log_reader_work_perform (logproto.h:100)
==5415==    by 0x50BA698: log_reader_io_process_input (logreader.c:191)


-- 
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.


More information about the syslog-ng mailing list