From owner-freebsd-performance@FreeBSD.ORG  Fri Apr  4 12:44:27 2008
Return-Path: <owner-freebsd-performance@FreeBSD.ORG>
Delivered-To: freebsd-performance@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 0B4D4106574B
	for <freebsd-performance@freebsd.org>;
	Fri,  4 Apr 2008 12:44:25 +0000 (UTC)
	(envelope-from fw@deneb.enyo.de)
Received: from mail.enyo.de (mail.enyo.de [IPv6:2001:14b0:202:1::a7])
	by mx1.freebsd.org (Postfix) with ESMTP id B4E0C8FC14
	for <freebsd-performance@freebsd.org>;
	Fri,  4 Apr 2008 12:44:22 +0000 (UTC)
	(envelope-from fw@deneb.enyo.de)
Received: from deneb.vpn.enyo.de ([212.9.189.177] helo=deneb.enyo.de)
	by mail.enyo.de with esmtp id 1JhlH4-0001z5-Ey;
	Fri, 04 Apr 2008 14:44:06 +0200
Received: from fw by deneb.enyo.de with local (Exim 4.69)
	(envelope-from <fw@deneb.enyo.de>)
	id 1JhlH3-00010x-IW; Fri, 04 Apr 2008 14:44:05 +0200
From: Florian Weimer <fw@deneb.enyo.de>
To: JINMEI Tatuya / =?utf-8?B?56We5piO6YGU5ZOJ?= <Jinmei_Tatuya@isc.org>
References: <475B0F3E.5070100@fsn.hu> <m2lk6g71bc.wl%Jinmei_Tatuya@isc.org>
	<479DFE74.8030004@fsn.hu> <m2k5ltke09.wl%Jinmei_Tatuya@isc.org>
	<479F02A7.9020607@fsn.hu> <m24pcwt5b7.wl%Jinmei_Tatuya@isc.org>
	<47A614E9.4030501@fsn.hu> <m2wspkpl7r.wl%Jinmei_Tatuya@isc.org>
	<47A77A13.6010802@fsn.hu> <m2zlueohxk.wl%Jinmei_Tatuya@isc.org>
	<47B1D2F4.5070304@fsn.hu> <m2tzkexdo7.wl%Jinmei_Tatuya@isc.org>
	<47B2DD62.6020507@fsn.hu> <m2abm4y4by.wl%Jinmei_Tatuya@isc.org>
	<47BAE0B3.4090004@fsn.hu> <m2pruse24g.wl%Jinmei_Tatuya@isc.org>
	<m2skzns3eh.wl%Jinmei_Tatuya@isc.org>
Date: Fri, 04 Apr 2008 14:44:05 +0200
In-Reply-To: <m2skzns3eh.wl%Jinmei_Tatuya@isc.org> ("JINMEI Tatuya /
	=?utf-8?B?56We5piO6YGU5ZOJ?=
	"'s message of "Wed, 20 Feb 2008 13:51:02 -0800")
Message-ID: <87abk9yelm.fsf@mid.deneb.enyo.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Fri, 04 Apr 2008 13:14:37 +0000
Cc: Attila Nagy <bra@fsn.hu>, freebsd-performance@freebsd.org,
	bind-users@isc.org
Subject: Re: max-cache-size doesn't work with 9.5.0b1
X-BeenThere: freebsd-performance@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Performance/tuning <freebsd-performance.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-performance>,
	<mailto:freebsd-performance-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-performance>
List-Post: <mailto:freebsd-performance@freebsd.org>
List-Help: <mailto:freebsd-performance-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-performance>,
	<mailto:freebsd-performance-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2008 12:44:27 -0000

* JINMEI Tatuya / =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89:

> Then the named process will eventually abort itself with a core dump
> due to malloc failure.  Please show us the stack trace at that point.
> Hopefully it will reveal the malloc call that keeps consuming memory.

I've successfully used a backtrace()-instrumented malloc() to track down
difficult memory leaks.  backtrace() is necessary because it allows you
to see past malloc() wrappers.

(backtrace() seems to be part of libexecinfo on FreeBSD.)