Very critical: Memory leak in freeradius-1.1.6

[nikitha george]

On 5/20/07, Alan DeKok <aland at deployingradius.com> wrote:
>>> If valgrind doesn't say that the memory is lost, then the memory is
very likely still being used.  i.e. It's likely needed for something.

something..?
Why do radiusd need to hold the memory even after cleaning up the request?
Even after stopping the request, the memory never gets freed. Why is this
strange result of huge memory usage by radiusd?


On 5/20/07, Alan DeKok <aland at deployingradius.com> wrote:
>
> nikitha george wrote:
> > The memory usage of radiusd in our system went from 6687KB to 160MB
> > which is 50.1% of memory of our system and radiusd got re-started.
>
>   160Mb does sound like a lot.
>
> > I had run the Valgrind to see the resource leak. Definitely lost memory
> > was 380 Bytes but still reachable are more. I think this is the one
> > which is leaking memory. I dont have access to the log files today, i
> > will post it by tomorrow for your reference.
>
>   The 380 bytes "definitely lost" is from libltdl.  It contributed
> almost nothing to the 160M total memory used by the server.
>
>   If valgrind doesn't say that the memory is lost, then the memory is
> very likely still being used.  i.e. It's likely needed for something.
>
>   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/users.html
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20070521/97010e45/attachment.html>