There are memory leaks with SIGHUP about unbound

[wcawijngaards]

For THP, transparent huge pages in madvise, I do not easily see how it could help since Unbound does not really have unused mapped memory sitting around.

I also think the issue can be closed. Thank you for the participation.

[eaglegai]

I have read run_daemon\daemon_cleanup\daemon_fork\daemon_create_workers\worker_delete functions, but have no idea what's wrong, could you help me?@wcawijngaards @gthess

[wcawijngaards]

A quick check with valgrind, shows that unbound has no memory leaks after a couple kill -HUP on it. I can see that the rss increases as well, with some size after the reloads, but valgrind reports no memory leaks. Perhaps it is something like memory fragmentation.

[yvoinov]

Sure. Looks like memory fragmentation. Unbound is significantly fragments RAM quite strongly (About 40%).

I can confirm that there are no significant memory leaks.

[Forza-tng]

Would THP be helpful here? There is madvise that a process could use, unless the sysadmin forces THP.

[eaglegai]

@wcawijngaards @yvoinov if you don't mind, I want to close the issue， thanks for your reply~