[syslog-ng] Re: RE: Re: syslog-ng 2.0rc1 memory usage
bazsi at balabit.hu
Sun Sep 10 10:40:24 CEST 2006
Thanks for this report, I finally had time to track these down. My vpn
connection does not work currently, so I'm unable to commit it right
now, but hopefully it'll be committed by tomorrow.
On Wed, 2006-08-09 at 08:18 -0500, Martin, David M wrote:
> here are the definitely lost record results.
> short duration (start valgrind, send hup, wait, send hup, kill)
> ==7989== 70 bytes in 1 blocks are definitely lost in loss record 15 of 43
> ==7989== at 0x1B904984: malloc (vg_replace_malloc.c:131)
> ==7989== by 0x12AB72: g_malloc (in /usr/lib/libglib-2.0.so.0.400.7)
> ==7989== by 0x1394F5: g_strdup (in /usr/lib/libglib-2.0.so.0.400.7)
> ==7989== by 0x80559B6: log_writer_options_init (logwriter.c:507)
> ==7989== 1080 bytes in 10 blocks are definitely lost in loss record 35 of 43
> ==7989== at 0x1B905301: calloc (vg_replace_malloc.c:176)
> ==7989== by 0x12ABDF: g_malloc0 (in /usr/lib/libglib-2.0.so.0.400.7)
> ==7989== by 0x80530FD: log_msg_new (logmsg.c:545)
> ==7989== by 0x805BE42: log_reader_handle_line (logreader.c:178)
> ==7989== LEAK SUMMARY:
> ==7989== definitely lost: 1150 bytes in 11 blocks.
> ==7989== possibly lost: 0 bytes in 0 blocks.
> ==7989== still reachable: 113453 bytes in 1157 blocks.
> ==7989== suppressed: 200 bytes in 1 blocks.
More information about the syslog-ng