Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 28 Sep 2017 07:57:01 +0200
From:      "O. Hartmann" <ohartmann@walstatt.org>
To:        Hans Petter Selasky <hps@selasky.org>
Cc:        Guido Falsi <madpilot@FreeBSD.org>, "O. Hartmann" <ohartmann@walstatt.org>, freebsd-current <freebsd-current@freebsd.org>
Subject:   Re: net/asterisk13: memory leak under 12-CURRENT?
Message-ID:  <20170928075701.23ca8b10@freyja.zeit4.iv.bundesimmobilien.de>
In-Reply-To: <31faf367-69e2-b7e3-dd14-67bf69a67ec2@selasky.org>
References:  <20170926144522.21e59cfe@freyja.zeit4.iv.bundesimmobilien.de> <979b6cfe-0e38-5df3-7bb5-cdb8de6677bf@FreeBSD.org> <20170926154155.28deb2e1@freyja.zeit4.iv.bundesimmobilien.de> <b0a72fdb-ad41-abab-fbde-4caa73799719@FreeBSD.org> <31faf367-69e2-b7e3-dd14-67bf69a67ec2@selasky.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 27 Sep 2017 12:51:18 +0200
Hans Petter Selasky <hps@selasky.org> wrote:

> On 09/27/17 09:05, Guido Falsi wrote:
> > On 09/26/2017 15:41, O. Hartmann wrote:  
> >> On Tue, 26 Sep 2017 15:06:23 +0200
> >> Guido Falsi <madpilot@FreeBSD.org> wrote:  
> >   
> >> Since I run net/asterisk with automatic module loading (I'm new to
> >> asterisk), this is very likely and might cause the problem somehow.
> >>  
> > 
> > You can exclude single modules from autoloading via modules.conf.
> >   
> >>> Not sure, restarting the daemon should free any leaked memory the daemon
> >>> has. If a killed process leaves memory locked at the system level there
> >>> should be some other cause.  
> >>
> >> Even with no runnidng asterisk, memory level drops after the last shutdown
> >> of asterisk and keeps that low. Even for weeks! My router never shows that
> >> high memory consumption, even under load.  
> > 
> > But while asterisk is running does the memory usage increase unbounded
> > till filling all available memory or does it stabilize at some point?
> > 
> > Asterisk is relatively memory hungry, especially with all modules
> > enabled. It also caches and logs various information in RAM, even doing
> > "nothing" it will cache and log that "nothing" activity. If memory does
> > stabilize after some point it's not really a leak but it's standard
> > memory usage. To reduce it you should disable all unused modules.
> >   
> >>
> >> The question would be: how to use vmstat to give hints for those familiar
> >> with memory subsystems to indicate a real bug?
> >>
> >> I tried to find some advices, but maybe my English isn't good enough to
> >> make google help.  
> > 
> > I'm not able to give you a correct indication, but if the memory usage
> > is not increasing indefinitely but is stabilizing I'd say it's not
> > really a leak.
> >   
> 
> Did you look at the output from "vmstat -m" and "vmstat -z" ?
> 
> --HPS

I did not, but now I will ;-)

Thanks for the hint!

Kind regards,
Oliver



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170928075701.23ca8b10>