[syslog-ng] [Bug 278] Many memory leak problems happen when do configuration reloading

bugzilla at bugzilla.balabit.com bugzilla at bugzilla.balabit.com
Wed Apr 16 05:33:42 CEST 2014


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





--- Comment #6 from Xufeng Zhang <xufeng.zhang at windriver.com>  2014-04-16 05:33:42 ---
(In reply to comment #5)
> Created an attachment (id=99)
 --> (https://bugzilla.balabit.com/attachment.cgi?id=99) [details]
> Don't allocate a new buffer if fails to consume current item
> 

After apply this patch, below valgrind memory leak disappears:
==25796== 3,072 bytes in 3 blocks are definitely lost in loss record 616 of 622
==25796==    at 0x4A05F58: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==25796==    by 0x3B742478F4: g_malloc (in /lib64/libglib-2.0.so.0.2600.0)
==25796==    by 0x3B74E3D1D8: log_writer_flush (logwriter.c:974)
==25796==    by 0x3B74E3D2BC: log_writer_work_perform (logwriter.c:163)
==25796==    by 0x3B74E3D327: log_writer_io_flush_output (logwriter.c:243)
==25796==    by 0x3B74E63666: iv_fd_poll_and_run (iv_fd.c:167)
==25796==    by 0x3B74E63E13: iv_main (iv_main_posix.c:117)
==25796==    by 0x3B74E3D7E6: main_loop_run (mainloop.c:788)
==25796==    by 0x4017A0: main (main.c:267)

But I'm not sure whether or not it would introduce any side effect.


-- 
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