Re: net/asterisk13: memory leak under 12-CURRENT?

On Wed, 27 Sep 2017 09:05:42 +0200
Guido Falsi <madpilot_at_FreeBSD.org> wrote:

> On 09/26/2017 15:41, O. Hartmann wrote:
> > On Tue, 26 Sep 2017 15:06:23 +0200
> > Guido Falsi <madpilot_at_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.

I tried, but I need to study first more documentation to explore what is
prerequisite and what is optional.

> 
> >> 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?

As far as I could observe, a three day test run of the router/firewall/asterisk
box drained around 500 MB of memory: starting at boot time with ~3700 MB,
asterisk leaves the box with ~3640 MB after bein started and after three days
the system reached ~3150 MB. Stopping asterisk gave back some memory, so ~3300
MB then was for days the final result - not recovering anything further. I use
TEMPFS, if it matters, but I checked /tmp and /var/, there were no remnant
files so far. TMPVAR is only allowed to have 256 MB.
 
> 
> 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.
> 

Can't say whether it is stabilising or not - I think the runtime is too short.
I'll check first to disable some modules in the first place and then try to
perform a test with several days of asterisk enabled.