Hi, I just configured radius 1.1.3 and found that there are some memory leaks in it. Here is the output of Valgrind ==30841== ERROR SUMMARY: 4365 errors from 82 contexts (suppressed: 44 from 2) ==30841== malloc/free: in use at exit: 1,354,452 bytes in 25,976 blocks. ==30841== malloc/free: 35,826 allocs, 9,850 frees, 3,185,516 bytes allocated. ==30841== For counts of detected errors, rerun with: -v ==30841== searching for pointers to 25,976 not-freed blocks. ==30841== checked 75,458,816 bytes. ==30841== ==30841== ==30841== 11 bytes in 1 blocks are possibly lost in loss record 12 of 93 ==30841== at 0x43BF53F: malloc (m_replacemalloc/vg_replace_malloc.c:149) ==30841== by 0x441F567: (within /usr/lib/libltdl.so.3.1.0) ==30841== by 0x44200B1: (within /usr/lib/libltdl.so.3.1.0) ==30841== by 0x4420CB7: (within /usr/lib/libltdl.so.3.1.0) ==30841== by 0x4421881: lt_dlopenext (in /usr/lib/libltdl.so.3.1.0) ==30841== by 0x8052C5A: (within /usr/local/sbin/radiusd) ==30841== by 0x8052F66: find_module_instance (in /usr/local/sbin/radiusd) ==30841== by 0x8054564: (within /usr/local/sbin/radiusd) ==30841== by 0x805475B: compile_modsingle (in /usr/local/sbin/radiusd) ==30841== by 0x8053422: (within /usr/local/sbin/radiusd) ==30841== by 0x8053958: setup_modules (in /usr/local/sbin/radiusd) ==30841== by 0x805683D: main (in /usr/local/sbin/radiusd) ==30841== ==30841== ==30841== 97 bytes in 6 blocks are definitely lost in loss record 43 of 93 ==30841== at 0x43BF53F: malloc (m_replacemalloc/vg_replace_malloc.c:149) ==30841== by 0x441F567: (within /usr/lib/libltdl.so.3.1.0) ==30841== by 0x44200B1: (within /usr/lib/libltdl.so.3.1.0) ==30841== by 0x4420CB7: (within /usr/lib/libltdl.so.3.1.0) ==30841== by 0x4421881: lt_dlopenext (in /usr/lib/libltdl.so.3.1.0) ==30841== by 0x8052C5A: (within /usr/local/sbin/radiusd) ==30841== by 0x8052F66: find_module_instance (in /usr/local/sbin/radiusd) ==30841== by 0x8054564: (within /usr/local/sbin/radiusd) ==30841== by 0x805475B: compile_modsingle (in /usr/local/sbin/radiusd) ==30841== by 0x8053422: (within /usr/local/sbin/radiusd) ==30841== by 0x8053958: setup_modules (in /usr/local/sbin/radiusd) ==30841== by 0x805683D: main (in /usr/local/sbin/radiusd) ==30841== ==30841== ==30841== 476 bytes in 7 blocks are possibly lost in loss record 68 of 93 ==30841== at 0x43C0C58: calloc (m_replacemalloc/vg_replace_malloc.c:279) ==30841== by 0x8464EA: _dl_allocate_tls (in /lib/ld-2.3.3.so) ==30841== by 0xAB978D: pthread_create@@GLIBC_2.1 (in /lib/tls/libpthread-2.3.3.so) ==30841== by 0x8059A3E: (within /usr/local/sbin/radiusd) ==30841== by 0x8059D20: thread_pool_init (in /usr/local/sbin/radiusd) ==30841== by 0x8056A8B: main (in /usr/local/sbin/radiusd) ==30841== ==30841== LEAK SUMMARY: ==30841== definitely lost: 97 bytes in 6 blocks. ==30841== possibly lost: 487 bytes in 8 blocks. ==30841== still reachable: 1,353,868 bytes in 25,962 blocks. ==30841== suppressed: 0 bytes in 0 blocks. ==30841== Reachable blocks (those to which a pointer was found) are not shown. ==30841== To see them, rerun with: --show-reachable=yes Can any one help me how to fix this.? Best Regards, Abdul Qadir --------------------------------- Need a quick answer? Get one in minutes from people who know. Ask your question on Yahoo! Answers.
Abdul Qadir wrote:
Hi,
I just configured radius 1.1.3 and found that there are some memory leaks in it.
Here is the output of Valgrind
i.e. memory is not free'd when the process exits. This is not a "memory leak" that will affect anything. The only reason to fix these issues is to prevent valgrind from complaining about them. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
participants (2)
-
Abdul Qadir -
Alan DeKok