Freeradius crashes with SIGABRT
aland at deployingradius.com
Wed Dec 4 17:35:44 CET 2019
On Dec 4, 2019, at 11:31 AM, Daniel Feuchtinger <daniel.feuchtinger at lrz.de> wrote:
> I tried the Patch in commit 36656cc39f52dbc79f8b373d313281144eef205b
> with the 3.0.20 code, that resulted in a lot of
> memory leaks (109 of them within a few minutes):
That patch shouldn't cause memory leaks.
> ==33264==ERROR: LeakSanitizer: detected memory leaks
> Direct leak of 3168 byte(s) in 36 object(s) allocated from:
> #0 0x7efc8022b330 in __interceptor_malloc (/usr/lib/x86_64-linux-gnu/libasan.so.5+0xe9330)
> #1 0x7efc800f9ad8 in rad_malloc src/main/util.c:528
> #2 0x55fc419d8aef in server_pool_alloc src/main/realms.c:1016
The patch definitely won't cause that memory leak.
> The server did not crash but it stopped logging and
> probably working while producing the leaks.
> I'll try again with the current git code tomorrow.
More information about the Freeradius-Users