Garrett D'Amore wrote: > Iwan Aucamp wrote: >> Hi >> >> The memory leak - or atleast what appeared to be a memory leak >> (growing heap size) was only observed on libmalloc. >> >> After I sent the initial message I ran with libumem for 7 hours - and >> the heap size increase was sensible (7 MB for this time ) - as soon as >> i switched back to libmalloc the heap size started growing at a rate >> of more than 20 MB per minue - so this does seem to be related to way >> in which application uses heap and way in which libmalloc manages the >> heap. >> >> I will continue to use libumem and see how things work out. > > Sounds good. I'd recommend libumem anyway... the technology behind it > is well proven in the kernel. :-)
Plus, you can use it with gcore and mdb to check for _actual_ memory leaks, as opposed to just apparent heap growth. -- James Carlson 42.703N 71.076W <carls...@workingcode.com> _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
