[syslog-ng] Possible memleak in 3.3 HEAD

[Jakub Jankowski]

On Mon, 31 Oct 2011 22:16:21 +0100, Balazs Scheidler wrote:
> On Mon, 2011-10-31 at 12:17 +0100, Jakub Jankowski wrote:
> > 2. There are still some leaks; one of which is definitely triggered by
> > HUP. Full valgrind output files are available as:
> > http://toxcorp.com/stuff/syslog-ng-leak/s3.3.1-60b5967-HUP.log
> > http://toxcorp.com/stuff/syslog-ng-leak/s3.3.1-60b5967-noHUP.log
[...]
> Thanks for the detailed diagnosis, there was indeed a leak which can
> multiply on reload for each open (at the time of the reload),
> macro-based destination file.
> 
> commit 9e7f9258b03c58701be40d40f9708bb3a9c56625

I can confirm that current HEAD does not exhibit this leak any longer:

==25823== LEAK SUMMARY:
==25823==    definitely lost: 637 bytes in 14 blocks
==25823==    indirectly lost: 0 bytes in 0 blocks
==25823==      possibly lost: 13,071 bytes in 107 blocks
==25823==    still reachable: 78,991 bytes in 3,277 blocks
==25823==         suppressed: 0 bytes in 0 blocks

I've updated my production systems to 9e7f9258b and will observe its
behaviour over the next few days (but even 60b5967 looked promising).
Thanks for your help, it is much appreciated. Also sorry for being so
obtrusive about this issue :^)

Regards,

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