-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[defect]: Memory leak when reloading configuration using HUP signal #5490
Comments
Please verify that this is a leak, using something like The server will clean up the memory, after |
Sorry, I am not familiar with From what you says, taking in account that max_request_time=30, it should go down after 2 minutes. But here is the result after 5 minutes.
After 10 minutes i stopped the script and reverted the client.conf, and reloaded again. |
Hmm... well, this is a low priority issue. The short answer is don't HUP it that often, and if you're worried about memory, just restart it. We're happy to take patches to fix the issue, but at this point, it's not enough of a priority for us to spend time debugging it. |
I see, no worries. You are right. My scenario is too extreme and we can always restart the container. |
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
ps -aux
and remember the memory value in VSZ and PID/etc/freeradius/clients.conf
(for example add some spaces)kill -HUP <PID>
ps -aux
again and compare the memory value in VSZResult:
Starting from the second reload the VSZ will grow after each and every reload and never go back.
Log output from the FreeRADIUS daemon
Relevant log output from client utilities
not relevant
Backtrace from LLDB or GDB
The text was updated successfully, but these errors were encountered: