[syslog-ng] Possible memleak in 3.3 HEAD

[Jakub Jankowski]

On 2011-10-09, Balazs Scheidler wrote:

> On Wed, 2011-10-05 at 01:44 +0200, Jakub Jankowski wrote:
>> On Mon, 3 Oct 2011 14:34:13 +0200 (CEST), Jakub Jankowski wrote:
>>>
>> I think I spoke too soon. :-/
>> See attached cacti graph. This is basically an output of
>> awk '/VmRSS:/ { $print $2*1024 }'  /proc/$(cat /var/run/syslog-ng.pid)/status
>> on git head ("3.3.1" ATM). There must be something else going on; any hints
>> on how to diagnose this?
>
> It definitely seems to be a leak of some kind. If at all possible,
> running it for some time under valgrind like you did previously would be
> tremendous.

I've run half my "live" traffic for approx. 5 minutes through another 
node, with syslog-ng 3.3.1 running under valgrind. Log available at:
http://toxcorp.com/stuff/syslog-ng-leak/s3.3.1-prod-half-5min.log
Does it ring any bells (it doesn't for me). Should I test it longer?


Regards,

-- 
Jakub Jankowski|shasta at toxcorp.com|http://toxcorp.com/
GPG: FCBF F03D 9ADB B768 8B92 BB52 0341 9037 A875 942D