I had the same issue, but couldn't reproduce it when running under valgrind. I wasn't using json and redis, either. I submitted https://github.com/balabit/syslog-ng/issues/446 for this, which includes a copy of my config file.

I need to set up a test environment so that reproducing the issue doesn't require me to lose real messages before I can proceed further, but maybe you can help out.

-Pradeep


On Apr 29, 2015, at 7:19 PM, Jim Hendrick <jrhendri@roadrunner.com> wrote:


From 3.6.2 OSE built with json & redis

Seeing steady memory growth (> 10 GB after ~ a day at ~7000 EPS load)

This was from a few minutes of runtime. (~5)

Is this a known issue or did I trip over something?

Thanks!
Jim



<valgrind.err.gz>______________________________________________________________________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.balabit.com/wiki/syslog-ng-faq