From owner-freebsd-current@FreeBSD.ORG  Wed Jun 14 17:53:54 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4B14016A41A;
	Wed, 14 Jun 2006 17:53:54 +0000 (UTC)
	(envelope-from jd@ugcs.caltech.edu)
Received: from groat.ugcs.caltech.edu (groat.ugcs.caltech.edu
	[131.215.176.110])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0D22B43D45;
	Wed, 14 Jun 2006 17:53:53 +0000 (GMT)
	(envelope-from jd@ugcs.caltech.edu)
Received: by groat.ugcs.caltech.edu (Postfix, from userid 3640)
	id D4A915880B; Wed, 14 Jun 2006 10:53:52 -0700 (PDT)
Date: Wed, 14 Jun 2006 10:53:52 -0700
From: Paul Allen <nospam@ugcs.caltech.edu>
To: Jason Evans <jasone@freebsd.org>
Message-ID: <20060614175352.GI28128@groat.ugcs.caltech.edu>
References: <448FC3AF.9060606@bulinfo.net> <200606141023.51185.jhb@freebsd.org>
	<449048C7.6090109@FreeBSD.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <449048C7.6090109@FreeBSD.org>
Sender: jd@ugcs.caltech.edu
Cc: freebsd-current@freebsd.org, Krassimir Slavchev <krassi@bulinfo.net>
Subject: Re: memory leak in free()
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jun 2006 17:53:54 -0000

>From Jason Evans <jasone@freebsd.org>, Wed, Jun 14, 2006 at 10:35:03AM -0700:
> This is on a 32-bit system, right?  If so, what's happening is that the 
> brk-managed space (data segment) is being fragmented, such that the 
> address space isn't returned to the OS.  However, this is not really a 
> memory leak, since madvise() is called in order to let the kernel know 
> that the unused space need not be swapped out.

And in particular this should manifest itself as 'RES' declining but 'SIZE'
in top remaining unchanged.  Until an over-commit hating individual manages
to get a patch into the tree, this should not be a concern at all.

                             Paul