[syslog-ng] [Bug 257] memory leak on reload

bugzilla at bugzilla.balabit.com bugzilla at bugzilla.balabit.com
Fri Nov 1 21:47:01 CET 2013


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





--- Comment #3 from Evan Rempel <erempel at uvic.ca>  2013-11-01 21:47:01 ---
OK. I can easily produce this on my test system with NO messages going to it.

valgrind reports

[root at pangolin log]# cat valgrind.out
==2726== Memcheck, a memory error detector
==2726== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==2726== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==2726== Command: /usr/local/sbin/syslog-ng --cfgfile=/usr/local/etc/syslog-ng/syslog-ng.server.conf --persist-file=/var/local/syslog-ng.server.persist
--pidfile=/var/run/syslog-ng.server.pid --control=/var/local/syslog-ng.server.ctl --process-mode background
==2726== Parent PID: 16184
==2726== 
==2726== Warning: noted but unhandled ioctl 0x5422 with no size/direction hints
==2726==    This could cause spurious value errors to appear.
==2726==    See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper.
==2726== 
==2726== HEAP SUMMARY:
==2726==     in use at exit: 16,335 bytes in 51 blocks
==2726==   total heap usage: 104 allocs, 53 frees, 70,285 bytes allocated
==2726== 
==2726== LEAK SUMMARY:
==2726==    definitely lost: 216 bytes in 1 blocks
==2726==    indirectly lost: 1,991 bytes in 26 blocks
==2726==      possibly lost: 2,054 bytes in 8 blocks
==2726==    still reachable: 12,074 bytes in 16 blocks
==2726==         suppressed: 0 bytes in 0 blocks
==2726== Rerun with --leak-check=full to see details of leaked memory
==2726== 
==2726== For counts of detected and suppressed errors, rerun with: -v
==2726== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 6 from 6)

Did you want binaries, core dump, recompile with -g ... just let me know.

I have added an attachment with the --leak-check=full output


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