crash in syslog-ng

I have three separate machines M1, M2 and M3. M1 and M2 send logs on some port to M3 using syslog-ng.

If i dont start syslog-ng on M3 does it have any effect on M1 or/and M2?

I am using libsyslog-ng-3.5.4.1, i know its old, i cannot do much about it.

Without running syslog-ng on M3(commented the launch on M3, but not on M1 and M2) , i booted 3 machines.
After boot, M1 and M2 syslog-ng is not started (or i dont know what happened , not enough logs in dmesg w.r.t syslog)

so i manually started the syslog-ng on M1 (also M2 separtely)

after few mins i see below log.

Code:*** Error in `/usr/sbin/syslog-ng': double free or corruption (!prev): 0x08057d50 ***
======= Backtrace: =========
/lib/libc.so.6(+0x649cb)[0x402c99cb]
/lib/libc.so.6(+0x6ef17)[0x402d3f17]
/lib/libc.so.6(+0x6f6c1)[0x402d46c1]
/usr/lib/libglib-2.0.so.0(g_free+0x20)[0x40130b20]
/usr/lib/libsyslog-ng-3.5.4.1.so(+0x441a7)[0x4006b1a7]
/usr/lib/libsyslog-ng-3.5.4.1.so(+0x4433f)[0x4006b33f]
/usr/lib/libsyslog-ng-3.5.4.1.so(+0x2c550)[0x40053550]
/usr/lib/libsyslog-ng-3.5.4.1.so(+0x2c6d4)[0x400536d4]
/usr/lib/libsyslog-ng-3.5.4.1.so(+0x2c731)[0x40053731]
/usr/lib/libsyslog-ng-3.5.4.1.so(iv_fd_poll_and_run+0xc3)[0x400782c3]
/usr/lib/libsyslog-ng-3.5.4.1.so(iv_main+0x4a)[0x40078cea]
/usr/lib/libsyslog-ng-3.5.4.1.so(main_loop_run+0x136)[0x40055256]
/usr/sbin/syslog-ng(main+0x187)[0x8048ff7]
/lib/libc.so.6(__libc_start_main+0xf7)[0x4027d467]
/usr/sbin/syslog-ng[0x80490eb]I am confused now, because i am not sure that error i am getting because syslog-ng is not running on M3 or some other reason.