memory leak in free()

Kostik Belousov kostikbel at gmail.com
Wed Jun 14 18:40:36 UTC 2006


On Wed, Jun 14, 2006 at 01:58:46PM -0400, John Baldwin wrote:
> On Wednesday 14 June 2006 13:53, Paul Allen wrote:
> > From Jason Evans <jasone at 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.
> 
> And any such patch would have to have a knob that defaulted to keeping
> overcommit on anyway. :-)
Ha ! Exactly. My patch has such knob :).
Shameless plug: http://kostikbel.narod.ru/overcommit

Testing the patch on recent CURRENT, I did notice that jemalloc
really likes the swap :).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20060614/6a318826/attachment.pgp


More information about the freebsd-current mailing list