1 Aug 2011 12:39
Re: 3.3.0beta1 leaking memeory (Re: syslog-ng 3.3.0beta & ESX crashes)
Balazs Scheidler <bazsi <at> balabit.hu>
2011-08-01 10:39:54 GMT
2011-08-01 10:39:54 GMT
Hi, Thanks for the info, I'll try to look at this today. On Fri, 2011-07-22 at 14:04 +0200, Gergely Nagy wrote: > Gergely Nagy <algernon <at> balabit.hu> writes: > > > Hendrik Visage <hvjunk <at> gmail.com> writes: > > > >> I've mailed Gergely the Valgrind output to analyze 3.3.0beta1 memory > >> leak(s), so if anybody else are interested in it, please contact me > >> for them. > > > > I had a little time to look into the memory leak issue, and I can > > confirm: the leak happens all the time with latest git. > > After a bit of bisecting, this is what i found to be the cause of the > massive leak: > > b8cc9fe3bb41d862918d9e39b0ded812dd756ef5 is the first bad commit > commit b8cc9fe3bb41d862918d9e39b0ded812dd756ef5 > Author: Balazs Scheidler <bazsi <at> balabit.hu> > Date: Thu Jul 14 12:26:01 2011 +0200 > > delegate flow-control early-ack decision to destination drivers > > Sources always expect an acknowledgement for each message they produce. > This acknowledgement is usually generated when all the destinations have > finished their processing of the given message, unless flow-control > is disabled.(Continue reading)
RSS Feed