[syslog-ng] Possible memleak in 3.3 HEAD

[Jakub Jankowski]

On 2011-10-03, Balazs Scheidler wrote:
> On Mon, 2011-10-03 at 00:14 +0200, Jakub Jankowski wrote:
>> On Tue, 27 Sep 2011 20:16:29 +0200, Balazs Scheidler wrote:
>>
>> Having issues building el5 package directly from git (see my other mails in
>> this thread), I chose only to apply 2ed7f92153aec5e4e666ea17dcd8d2232a8e76f9
>> and e224d45da2ecad68f7f9c44895849a0fc795aae5 commits to the source I'm
>> building from, which is essentially 0a3d844ff94a14d770bcdfa993f02e87e58a81f2.
>>
>> Unfortunately, those two patches do not seem to help, I'm still getting this
>> in valgrind output on my test machine:
[...]
>> So, either 1) those two patches are not sufficent to fix this bug,
>> 2) those patches do not fix *this* bug, or 3) PEBKAC, and I'm doing something
>> wrong (very likely!).
>
> Strange, I've successfully reproduced the leak without the patches and
> they were fixed with them. Let's see if 3.3.1 solves the issue or not.

As strange as it was, it seems really fixed with git HEAD. Using dist 
tarball Gergely provided (thanks again), I've built 
70fa96f33c89ce2bb10d10aaa7ba0492764a441c and ran my tests. Results are 
comforting:

$ grep -A 6 'LEAK SUMMARY' s3.3.1-70fa96f33c89ce2bb10d10aaa7ba0492764a441c-const.log
==28094== LEAK SUMMARY:
==28094==    definitely lost: 101 bytes in 2 blocks
==28094==    indirectly lost: 1,010 bytes in 21 blocks
==28094==      possibly lost: 12,919 bytes in 106 blocks
==28094==    still reachable: 76,628 bytes in 3,275 blocks
==28094==         suppressed: 0 bytes in 0 blocks
==28094==
$ grep -A 6 'LEAK SUMMARY' s3.3.1-70fa96f33c89ce2bb10d10aaa7ba0492764a441c-random.log
==30031== LEAK SUMMARY:
==30031==    definitely lost: 101 bytes in 2 blocks
==30031==    indirectly lost: 1,010 bytes in 21 blocks
==30031==      possibly lost: 12,919 bytes in 106 blocks
==30031==    still reachable: 76,628 bytes in 3,275 blocks
==30031==         suppressed: 0 bytes in 0 blocks
==30031==
$

It behaves the same no matter what files it creates. I'll soon see how 
it's doing on production systems. Thanks for the fix and help.

Regards,

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