On Oct 11, 2019, at 9:15 AM, Arnaud LAURIOU <arnaud.lauriou@renater.fr> wrote:
We are suspecting memory leak in FR 3.0.19 : process memory status show VmData always keep increasing leading to VmSwap use after a few days which also keep increasing.
I have 2 questions : - What are the compile options to use valgrind ? only flag --enable-developper ?||
valgrind is a run-time checker, and doesn't need any compile time changes. You just run: valgrind --tool=memcheck --leak-check=full radiusd -f ... Note that you will need the "-f".
- In the changelog for version 3.0.20 : some memories problems seems to be solved, do you know when this version will be released ? (if the release date is close, we can wait to test this release rather than 3.0.19)
As Matthew says, you can test it now. Alan DeKok.