freeradius memory leak after use detail file
aland at deployingradius.com
Tue Feb 3 14:29:16 CET 2015
On Feb 3, 2015, at 2:30 AM, Yanrui Hu <yhu at appannie.com> wrote:
> free radius 2.2.6
> it works well on production system and one day we change to not write
> accouting data to database directly, instead, we write it to detail disk
> file and sync to db latter.
> after this change we found the memory consumption increase day by day.
> with valgrind I test it in lab environment with same configuration.
> here is the output:
> anybody can help if this is leak and if newest 3.2.x already fixed it?
The information you posted doesn’t show a leak in the detail file reader.
The leak here is in the detail file writer. It leaks memory *once*, when the module starts up. And never again.
Can you reproduce the problem with a simplified configuration? Odds are that the problem isn’t where you expect, but is somewhere else.
More information about the Freeradius-Users