Re: FreeRadius 1.1.3 Memory Leak
Hi, I agree with you that this memory is not freed when the process exit. Actually the problem is why this keeps on grwoing. If i start the process and exit it the statistics are different If i send some authentication request, the memory which is not freed by the process at exit keeps on growing. Is there any solution for this. Please see the difference below. This Paragraph show when no request was sent ==811== LEAK SUMMARY: ==811== definitely lost: 108 bytes in 7 blocks. ==811== possibly lost: 340 bytes in 5 blocks. ==811== still reachable: 1,353,886 bytes in 25,961 blocks. ==811== suppressed: 0 bytes in 0 blocks. ==811== Reachable blocks (those to which a pointer was found) are not shown. ==811== To see them, rerun with: --show-reachable=yes This Paragraph show when few authentication requests were sent. ==842== LEAK SUMMARY: ==842== definitely lost: 108 bytes in 7 blocks. ==842== possibly lost: 476 bytes in 7 blocks. ==842== still reachable: 1,353,950 bytes in 25,963 blocks. ==842== suppressed: 0 bytes in 0 blocks. ==842== Reachable blocks (those to which a pointer was found) are not shown. ==842== To see them, rerun with: --show-reachable=yes Best Regards, Abdul Qadir Message: 2 Date: Thu, 07 Dec 2006 01:47:54 -0800 From: Alan DeKok Subject: Re: FreeRadius 1.1.3 Memory Leak To: FreeRadius developers mailing list Message-ID: <4577E34A.8070203@deployingradius.com> Content-Type: text/plain; charset=ISO-8859-1 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 ------------------------------ - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html End of Freeradius-Devel Digest, Vol 20, Issue 3 *********************************************** --------------------------------- Any questions? Get answers on any topic at Yahoo! Answers. Try it now.
Abdul Qadir wrote:
Actually the problem is why this keeps on grwoing. If i start the process and exit it the statistics are different If i send some authentication request, the memory which is not freed by the process at exit keeps on growing. Is there any solution for this. Please see the difference below.
The server caches requests and responses for a time, so if you kill the server immediately after a response is sent, there may be many requests and responses still in memory. i.e. memory *lost* while it is running is bad. Slow memory growth over time is bad. The problems you're seeing are likely unimportant. If you leave the server running, does it's total memory use grow over time? If not, there's probably no memory leak. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
participants (2)
-
Abdul Qadir -
Alan DeKok