From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 11 18:51:10 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A6FF16A407; Mon, 11 Sep 2006 18:51:10 +0000 (UTC) (envelope-from admin@intron.ac) Received: from intron.ac (unknown [210.51.165.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97ABB43D49; Mon, 11 Sep 2006 18:51:09 +0000 (GMT) (envelope-from admin@intron.ac) Received: from localhost (localhost [127.0.0.1]) (uid 1003) by intron.ac with local; Tue, 12 Sep 2006 02:51:07 +0800 id 0010E408.4505B01B.00012841 References: <200609100956.k8A9uD0P094639@repoman.freebsd.org> <200609111145.52446.jhb@freebsd.org> <20060911193600.7ab43fb6@Magellan.Leidinger.net> In-Reply-To: <20060911193600.7ab43fb6@Magellan.Leidinger.net> From: "Intron is my alias on the Internet" To: John Baldwin Date: Tue, 12 Sep 2006 02:51:07 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312"; format=flowed Content-Transfer-Encoding: 7bit Message-ID: Cc: freebsd-hackers@freebsd.org, Alexander Leidinger Subject: Re: PERFORCE change 105930 for review X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Sep 2006 18:51:10 -0000 Alexander Leidinger wrote: > Quoting John Baldwin (Mon, 11 Sep 2006 11:45:52 -0400): > >> On Sunday 10 September 2006 05:56, Alexander Leidinger wrote: >> > PROBLEMS: >> > >> > 1. Why does uma_zdestroy(9) print message like: >> > >> > Freed UMA keg was not empty (100 items). Lost 2 pages of memory. >> > >> > Does it represent any problems? >> >> It means a memory leak. > > Because this is verbatim from the submitter and I don't know if he is > subscribed to perforce@, we should tell him about it... CCed. :-) > > Bye, > Alexander. > But I have ensure that calling to uma_zalloc() and calling to uma_zfree() appear strictly in pair in my code. Even the simplest testing program can still lead to this kind of warning message (uma_zfree() is just next to uma_zalloc()): uma_zalloc(...); uma_zfree(...); ------------------------------------------------------------------------ From Beijing, China