1 Feb
2008
1 Feb
'08
4 p.m.
https://bugzilla.balabit.com/show_bug.cgi?id=18 --- Comment #3 from Balazs Scheidler <bazsi@balabit.hu> 2008-02-01 17:00:45 --- syslog-ng, just like GLib assumes that malloc() never fails, and aborts in this case. So the question is whether syslog-ng actually leaks memory, or it uses the available 128M for legitimate reasons (log_fifo_size for instance) The valgrind dump would be useful, but please use the following environment options: G_SLICE=always-malloc before starting valgrind. Thanks in advance. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.