Hello, I installed FR 2.2.1 from git on one of our radius servers on April 22. After installation, I ran valgrind memcheck against radiusd binary and it showed no memory leak. A few days later now, I ran valgrind again. It showed memory leak. I am not sure what caused it. I have valgrind memcheck output for you to review but its 7MB. I don't know if it's too big for posting or attaching it on this list. Please let me a way to post/send it without causing any trouble. I plan to upgrade our production server to 2.2.1 early next week and I am a little concerned with this memory leak check thing. Here is the radiusd -v: radiusd: FreeRADIUS Version 2.2.1 (git #c8eee19), for host i686-pc-linux-gnu, built on Apr 24 2013 at 11:10:03 Copyright (C) 1999-2013 The FreeRADIUS server project and contributors. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. You may redistribute copies of FreeRADIUS under the terms of the GNU General Public License. For more information about these matters, see the file named COPYRIGHT. And here is the last few lines of valgrind -tool=memcheck /usr/local/sbin/radiusd: ==25076== HEAP SUMMARY: ==25076== in use at exit: 4,054,108 bytes in 83,682 blocks ==25076== total heap usage: 117,041 allocs, 33,359 frees, 6,027,616 bytes allocated ==25076== ==25076== LEAK SUMMARY: ==25076== definitely lost: 16 bytes in 3 blocks ==25076== indirectly lost: 0 bytes in 0 blocks ==25076== possibly lost: 2,730,037 bytes in 59,322 blocks ==25076== still reachable: 1,324,055 bytes in 24,357 blocks ==25076== suppressed: 0 bytes in 0 blocks ==25076== Rerun with --leak-check=full to see details of leaked memory ==25076== ==25076== For counts of detected and suppressed errors, rerun with: -v ==25076== Use --track-origins=yes to see where uninitialised values come from ==25076== ERROR SUMMARY: 647193 errors from 416 contexts (suppressed: 113 from 10) Thanks, Yu Wang Network Architect ITS, FSU