From owner-freebsd-current@freebsd.org Thu Sep 28 05:57:08 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5311FE2994A for ; Thu, 28 Sep 2017 05:57:08 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BADB570DFD; Thu, 28 Sep 2017 05:57:06 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LcSWg-1dWOFs1vqo-00jrXV; Thu, 28 Sep 2017 07:57:02 +0200 Date: Thu, 28 Sep 2017 07:57:01 +0200 From: "O. Hartmann" To: Hans Petter Selasky Cc: Guido Falsi , "O. Hartmann" , freebsd-current 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> <31faf367-69e2-b7e3-dd14-67bf69a67ec2@selasky.org> Organization: Walstatt MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:FwtbhkqV/tNFeuiLvTMpNOzcYgYfcIjz5gg+GI7Juzd7CSBqYgl ZGNcSrXZEUuxZNiTHTWaFS7Wgi16sZf3HI/A2zKYzUYvQAq9r3hXbUfXVG1g7UHpO0SEepH GCACmJYATNef2bwhg0uRhY/6/YVtiVfNsyM3JPrwnEeODocfb4ivhUHCxZj2vQX9A+wDo4w +2NmJC1bjvH/2iRD5s0OA== X-UI-Out-Filterresults: notjunk:1;V01:K0:5C4uEzWwIcU=:02UaAp4A3R6b14c3gq1zWS waBZSeL9DQUVO/qxdLbXFjI+crRmr1UuUtb3UwDBeoT+tveO3DzOs6Y83rkrGuPym7japRqJw IXlkJGiso8jj08VELL+pkSSt14sd6OFqoXO4wWv39CQ/z8raV4FoJOzdPifT6CFI4wAECDkGx xliueOfGYV89K7EgfM3YPPIm5f39ZK5D/3pkTNYnTeXD7JGWMKNKi06ovQZl+C/5+WPxRzQF3 QE2txC4OnW7NMElkz1SGYaOJ9mZTgYbIwss0UARGABbeUVP/fQN+hkZIjynKvahoePVakvawH AfcP5W3xroiQTzOvNM8G8KSdxZKgeogmUnKMkS5Yl0JT39+gZ/5QFX+S3i1LLqOYkdMiYn/O1 wvaDlpQZ5+w5DFeQgVJkBfPVW99fM+/ri7Ia607+/w5ey2Gn0nMyxiIJI3uRAjHsYaFhyj3Ii 4ovqka4MAvV/gw9WLnjTXTcLuJZPPKqtjHhxEIovAaaeDvtzjwpgbZysDp+FMow5atux23mSi OtFcMntwI7fEL+lw5F0uZT7RLoZDbBU+9bAn4hQPQZOFLG2jRObhX9TZEY//4Lw/oKygUfNP9 V7QJbiRK0ycCGagb40yDGLOrfCSYCPTYL3pLnnGY140JybANqSvUsGkOgOvZoHpWmj5pIi/sK yK0/bjzNHCf3dYlhTZtB1RaGVqmvF9+nmr17xCXlmC3QFqVBUsDbs9ESb1QUW76+Bvm7Cma6c /N7XCO6JvNLfp2ydtnWq3rgBXckc5WsOEk9ntiWkNMfc4BcdRCm/UBQzZBISn7PyDChz7/fQc /7D8zogUBYOFglqEITZzkji4JWwWCS519aTgzEmVFhz7UI9qYM= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Sep 2017 05:57:08 -0000 On Wed, 27 Sep 2017 12:51:18 +0200 Hans Petter Selasky 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 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