Hi All, We have an issue from a customer who uses syslog-ng version 3.8.1 on the 3.10.108 kernel(Hardware: freescale-p2020ds-3.10-1.4). Customer observed a segmentation fault after syslog-ng being stuck for more than one hour. There are no reproducible steps available, the issue is seen as random. As per the backtrace segfault happened from "malloc_consolidate" which looks an odd behaviour.On checking the frame it looks mchunkptr "p" has the value 0x2 which caused this crash, but not been able to find out what is the root cause for this. Has there been any known issue with syslog-ng? Any idea if this issue is fixed in version 3.16.1. Any help or pointers would be appreciated. Attached the back trace. Back trace snippet: Program terminated with signal 11, Segmentation fault. #0 malloc_consolidate (av=av@entry=0xffc738c <main_arena>) at malloc.c:4070 4070 malloc.c: No such file or directory. (gdb) bt #0 malloc_consolidate (av=av@entry=0xffc738c <main_arena>) at malloc.c:4070 #1 0x0fec5cb4 in _int_malloc (av=av@entry=0xffc738c <main_arena>, bytes=bytes@entry=556) at malloc.c:3374 #2 0x0fec6f64 in __GI___libc_malloc (bytes=556) at malloc.c:2874 #3 0x0f90d58c in standard_malloc (n_bytes=<optimized out>) at gmem.c:85 #4 0x0f90d9f0 in g_malloc (n_bytes=n_bytes@entry=556) at gmem.c:159 #5 0x0f7be00c in log_msg_alloc (payload_size=256) at lib/logmsg/logmsg.c:1084 #6 log_msg_new_empty () at lib/logmsg/logmsg.c:1150 #7 0x0f7be088 in log_msg_new_local () at lib/logmsg/logmsg.c:1160 #8 0x0f7be194 in log_msg_new_mark () at lib/logmsg/logmsg.c:1260 #9 0x0f7713e8 in afinter_source_mark (s=0x10863690) at lib/afinter.c:142 #10 0x0f7c4c74 in iv_run_timers (st=st@entry=0x10284d30) at iv_timer.c:149 #11 0x0f7c72bc in iv_main () at iv_main_posix.c:107 #12 0x0f78b990 in main_loop_run () at lib/mainloop.c:497 #13 0x10001260 in main (argc=1, argv=0xbfbe7724) at syslog-ng/main.c:270 (gdb) Regards, Sam