Date: Tue, 08 Mar 2011 04:27:07 +0100 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-hackers@freebsd.org Subject: Re: Mem leak : malloc/free + pthreads = leakage? Message-ID: <il47md$hlr$1@dough.gmane.org> In-Reply-To: <AANLkTimV2d0aYjeQp-OBeOwdhNjTkVfg7d9ATtc=t7SP@mail.gmail.com> References: <40A52D4A-9397-4406-A7EC-E7CBBEFADD55@freebsd.org> <4D726887.5080800@rojer.pp.ru> <570723AB-7011-4185-89E1-E02F018DC0C3@ttel.com> <AANLkTikd22VT3CVtvkGdw6zos%2Biq4Ve8y1W_WLr0qctS@mail.gmail.com> <AANLkTi=K9QuK%2BbyxF1t7HzG9wKxXek804tNOgzM3Dp_b@mail.gmail.com> <AANLkTiksK3RYkbVCj6wphOLu5oxvUNKWRrBOJb8VaGXp@mail.gmail.com> <AANLkTimV2d0aYjeQp-OBeOwdhNjTkVfg7d9ATtc=t7SP@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/03/2011 18:35, Ryan Stone wrote: > On Sun, Mar 6, 2011 at 10:34 AM, Ryan Stone<rysto32@gmail.com> wrote: >> I would try playing with MALLOC_OPTIONS. I seriously doubt that there >> is an actual leak in jemalloc, but from my own experiences with it I >> suspect that there are certain multithreaded malloc/free sequences >> that interact badly with with the per-thread caching that jemalloc >> performs. The first thing I would try is setting MALLOC_OPTIONS=7h to >> disable the caching. >> > > Wait, sorry, apparently this is a new option in HEAD. Under 8.1 > MALLOC_OPTIONS=g will disable the thread-specific caching. See the > malloc(3) man page for the definitive list of available options. I can confirm this suspicion; I have an malloc-intensive multithreaded program on 8-STABLE which I need to run with MALLOC_OPTIONS g10f2n to reduce otherwise severe memory lossage by the allocator. I haven't tried it on 9, though.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?il47md$hlr$1>