Seems to be a hard case... Could you add --leak-check=full to valgrind. Sorry, I thought it was not necessary and without it the report is often more up to the point...
Rainer Sent from phone, thus brief. Am 31.10.2016 21:04 schrieb "matthew.gaetano" <[email protected]>: > rsyslog.log > <http://rsyslog-users.1305293.n2.nabble.com/file/n7591415/rsyslog.log> > > Sorry it took a little while. Instead of continuing to troubleshoot on our > primary we forwarded events to our secondary were we recreated the problem > as defined above. The output of the provided command is attached; i let it > run for aprox. 30-40min. > > ~Regards > > Matthew Gaetano > > > > -- > View this message in context: http://rsyslog-users.1305293. > n2.nabble.com/Liblognorm-User-Defined-Types-Memory-Leak- > tp7591408p7591415.html > Sent from the rsyslog-users mailing list archive at Nabble.com. > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > DON'T LIKE THAT. > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
