Memory leak in dual_tls_receive
aland at deployingradius.com
Wed Mar 4 13:56:01 CET 2015
On Mar 4, 2015, at 4:42 AM, Stefan Paetow <Stefan.Paetow at JISC.AC.UK> wrote:
>> I’ve pushed a fix. See commit #f3f13d18. It’s a one-line change to allocate the request with the correct parent context.
>> Once that change is done, the request->reply should be cleaned up, too.
> I'm assuming that this fix is in both the 3.0.x and master, right? If so, I'm still seeing the same behaviour that we reported to Sam (and that he investigated). :-/
Yes, the fix is in both places.
> I've been running 3.0.8 (head of 3.0.x) for 19 hours and memory usage grew from 0.7% (7348KB RSS) at 16:00 yesterday to 4.3% (44572KB RSS) around 9:40 this morning.
That’s not good. I’ll take a look at Sam’s other bug reports later today. The fix should be simple.
More information about the Freeradius-Devel