[syslog-ng] [Bug 160] memory leak in message buffering

[bugzilla at bugzilla.balabit.com]

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


Balazs Scheidler <bazsi at balabit.hu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bazsi at balabit.hu




--- Comment #4 from Balazs Scheidler <bazsi at balabit.hu>  2012-02-28 20:46:51 ---
This is odd, I could finally reproduce some kind of leak, but locally not all messages are leaked.
I'd have to do some more testing to diagnose the issue, I just wanted to let you know that I was working on this.

==26035== 378,508 (328,236 direct, 50,272 indirect) bytes in 905 blocks are definitely lost in loss record 622 of 622
==26035==    at 0x4C28F9F: malloc (vg_replace_malloc.c:236)
==26035==    by 0x591AF4F: g_malloc (gmem.c:131)
==26035==    by 0x4E5BD46: log_msg_new (logmsg.c:979)
==26035==    by 0x4E62B05: log_reader_work_perform (logreader.c:493)
==26035==    by 0x4E63298: log_reader_io_process_input (logreader.c:191)
==26035==    by 0x4E87705: iv_run_tasks (iv_task.c:62)
==26035==    by 0x4E8634C: iv_main (iv_main.c:253)
==26035==    by 0x4E696CD: main_loop_run (mainloop.c:731)
==26035==    by 0x4017EB: main (main.c:260)
==26035== 

The odd thing is that I've fed about 200000 messages and about 1000 was leaked. And I've stopped syslog-ng _after_ the full queue was sent to the perl program, 
so the queue should've been empty.


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