Date: Wed, 14 Jun 2006 10:53:52 -0700 From: Paul Allen <nospam@ugcs.caltech.edu> To: Jason Evans <jasone@freebsd.org> Cc: freebsd-current@freebsd.org, Krassimir Slavchev <krassi@bulinfo.net> Subject: Re: memory leak in free() Message-ID: <20060614175352.GI28128@groat.ugcs.caltech.edu> In-Reply-To: <449048C7.6090109@FreeBSD.org> References: <448FC3AF.9060606@bulinfo.net> <200606141023.51185.jhb@freebsd.org> <449048C7.6090109@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060614175352.GI28128>