Open
Description
What type of defect/bug is this?
Unexpected behaviour (obvious or verified by project member)
How can the issue be reproduced?
Tested using docker container freeradius/freeradius-server:3.2.6
- Run the container
- Attach to the container with another shell
- run
ps -aux
and remember the memory value in VSZ and PID - modify and save
/etc/freeradius/clients.conf
(for example add some spaces) - reload the configuration using
kill -HUP <PID>
- run
ps -aux
again and compare the memory value in VSZ - repeat steps 4,5,6 several times.
Result:
Starting from the second reload the VSZ will grow after each and every reload and never go back.
Log output from the FreeRADIUS daemon
not relevant
Relevant log output from client utilities
not relevant
Backtrace from LLDB or GDB
not relevant