[syslog-ng] Known memory leak issues in 3.3.4?

Peter Czanik czanik at balabit.hu
Thu Mar 22 14:55:54 CET 2012


On 03/22/2012 02:46 PM, Jakub Jankowski wrote:
> On Thursday 22 of March 2012, Marvin Nipper wrote:
>> After considerable effort, I managed to get 3.3.4 built (using gcc 4.4.2,
>> along with glib 2.29.92 and the requisite eventlog 0.2.12).  The problem
>> is that the resulting syslog-ng component grows continuously (at an
>> alarming rate).  Whereas my 3.0.5 syslog-ng process starts out running in
>> just under 3MB, and then stabilizes at about 3.3MB, the 3.3.4 version
>> starts out small, and then at the point where I killed it (about 2 hours
>> after starting it), it had already grown to 277MB.
> I know at least about one memory leak that has been once fixed, but then
> reintroduced between 3.3.2 and 3.3.3, and I think is present since then.
> I've mentioned it on this list in February:
> https://lists.balabit.hu/pipermail/syslog-ng/2012-February/018334.html
> It would be really nice if developers could take a look at the code again. :)
Check this: https://bugzilla.balabit.com/show_bug.cgi?id=160 The 
mentioned patch is available at 

Peter Czanik (CzP)<czanik at balabit.hu>
BalaBit IT Security / syslog-ng upstream

More information about the syslog-ng mailing list