Oh ya. Redhat 6 % cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.2 (Santiago) % uname -a Linux xxx 2.6.32-220.4.1.el6.x86_64 #1 SMP Thu Jan 19 14:50:54 EST 2012 x86_64 x86_64 x86_64 GNU/Linux Evan Rempel wrote:
Gergely Nagy wrote:
Evan Rempel <erempel@uvic.ca> writes:
I am fairly certain that there is a memory leak. How do I help track it down? Looking at your config, I don't recall any known problems in those areas, but I'll try to reproduce the problem.
Meanwhile, if you have time, running syslog-ng under valgrind would be very, very useful. If you do that, please set the G_SLICE environment variable to always-malloc, otherwise due to glib's allocator, the results will be severley screwed and hardly usable.
Yup, I can reproduce it. The output of valgrind does not appear to show the leak. If I run syslog-ng and do NOT send any data to it (it processes no log lines) the output of valgrind is the same as if it processes 100,000 log lines, however, when I "dump" 100,000 log lines
% wc /home1l/erempel/log 107590 1233928 18956930 /home1l/erempel/log
into the pipe (cat /home1l/erempel/log > pipe) the memory footprint of syslog-ng grows by 3MB, every time I dump in the log lines.
I have attached the config file and two valgrind outputs.
-- Evan Rempel erempel@uvic.ca Senior Systems Administrator 250.721.7691 Unix Services, University Systems, University of Victoria