<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>
<div>Queues are often full. (separate issue ).</div><div><br></div><div><br></div><div><br></div><div><br></div><div id="composer_signature"><div style="font-size:85%;color:#575757">Sent from my Verizon Wireless 4G LTE smartphone</div></div><br><br>-------- Original message --------<br>From: Fabien Wernli <wernli@in2p3.fr> <br>Date: 04/29/2015 9:55 AM (GMT-05:00) <br>To: syslog-ng@lists.balabit.hu <br>Subject: Re: [syslog-ng] syslog-ng memory leak ? valgrind attached <br><br>Hi Jim,<br><br>On Wed, Apr 29, 2015 at 09:49:05AM -0400, Jim Hendrick wrote:<br>> From 3.6.2 OSE built with json & redis<br>> <br>> Seeing steady memory growth (> 10 GB after ~ a day at ~7000 EPS load)<br>> <br>> This was from a few minutes of runtime. (~5)<br>> <br>> Is this a known issue or did I trip over something?<br><br>We're having similar issues when the workload tickles your figures.<br>One possible explanation seems to be that the memory from queues is never<br>released [1]. Are your queues always empty or do they do regular work?<br><br>Oh, then there was this one too [2]<br><br>[1] https://github.com/balabit/syslog-ng/issues/287<br>[2] https://github.com/balabit/syslog-ng/issues/446<br>______________________________________________________________________________<br>Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng<br>Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng<br>FAQ: http://www.balabit.com/wiki/syslog-ng-faq<br><br></body></html>