[syslog-ng] 3.3.0beta1 leaking memeory (Re: syslog-ng 3.3.0beta & ESX crashes)

[Hendrik Visage]

Hi there,

 I've mailed Gergely the Valgrind output to analyze 3.3.0beta1 memory
leak(s), so if anybody else are interested in it, please contact me
for them.

 I've since compiled 3.2.4+noescape patch (since only 3.3.0+ have the
default option for SQL insert I need/use for the autoincrementing ID
field in systemevents), and using the same config file (other than
@version 3.2 and the noescape('default') for my postgresql insertions)
and the system is  stable with no descernable memory growth compared
to syslog-ng 3.3.0beta1's explosion in memory size.

Hendrik

On Mon, Jul 18, 2011 at 3:02 PM, Gergely Nagy <algernon at balabit.hu> wrote:
> Hendrik Visage <hvjunk at gmail.com> writes:
>
>> Hi Gergely,
>>
>>  Looks like I have a syslog-ng 3.3beta1 (fetched from GITHEAD) that is
>> having a serious memory leak (and I'm not yet pushing all our logs to
>> it ;(
>>
>> Any advice in how to help you  track this problem?
>
> Hrm. Well, valgrind would be best, but that slows things down to almost
> a grounding halt. (But in case you want to try that:
> G_SLICE=always-malloc valgrind --leak-check=full -v --show-reachable-yes
> --log-file=valgrind.log syslog-ng -F would be the command to run ;)
>
> Other than that, a config could be useful, so I can try and reproduce
> the problem (or at least identify possible areas where the leak might be
> coming from, and go from there), and see if I can fix it.
>
> --
> |8]
>
> ______________________________________________________________________________
> 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
>
>