From owner-freebsd-current@freebsd.org Wed Sep 27 10:23:33 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 0B68AE30638 for ; Wed, 27 Sep 2017 10:23:33 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from mail.madpilot.net (grunt.madpilot.net [78.47.145.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C0B386C976 for ; Wed, 27 Sep 2017 10:23:32 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 3y2DRv5WsrzZrX; Wed, 27 Sep 2017 12:23:23 +0200 (CEST) Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10024) with ESMTP id 6tGYyQdnvMgj; Wed, 27 Sep 2017 12:23:21 +0200 (CEST) Received: from marvin.madpilot.net (micro.madpilot.net [88.149.173.206]) by mail.madpilot.net (Postfix) with ESMTPSA; Wed, 27 Sep 2017 12:23:21 +0200 (CEST) Subject: Re: net/asterisk13: memory leak under 12-CURRENT? To: "O. Hartmann" Cc: "O. Hartmann" , freebsd-current References: <20170926144522.21e59cfe@freyja.zeit4.iv.bundesimmobilien.de> <979b6cfe-0e38-5df3-7bb5-cdb8de6677bf@FreeBSD.org> <20170926154155.28deb2e1@freyja.zeit4.iv.bundesimmobilien.de> <20170927112706.436500ec@freyja.zeit4.iv.bundesimmobilien.de> From: Guido Falsi Message-ID: <40903499-6cbb-53b7-e25a-1d7d96c47a75@FreeBSD.org> Date: Wed, 27 Sep 2017 12:23:20 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <20170927112706.436500ec@freyja.zeit4.iv.bundesimmobilien.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit 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: Wed, 27 Sep 2017 10:23:33 -0000 On 09/27/2017 11:27, O. Hartmann wrote: > On Wed, 27 Sep 2017 09:05:42 +0200 > Guido Falsi wrote: >> 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. > These numbers really don't tell us anything. The system has anyway been running for days, depending on configuration daemons like cron and ntp are running and performing tasks, things are being cached and so on, so that difference after three days could be perfectly normal overhead. You need to investigate the amount of memory allocated to asterisk with ps and top and check if that stabilizes. A few days, at most a week would be enough. After that, if it's not stabilizing you can start thinking on a leak, but still can't assume where the leak is happening. > 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. > Whatever you prefer, but trying a few days uptime with all modules enabled is zero cost and east to do. Also you started this report with THIS configuration, changing configuration would prevent from comparing results. Let's test one thing at a time. -- Guido Falsi