Date: Sun, 6 Mar 2011 12:35:03 -0500 From: Ryan Stone <rysto32@gmail.com> To: Vlad Galu <dudu@dudu.ro> Cc: Deomid Ryabkov <myself@rojer.pp.ru>, Eric Anderson <anderson@ttel.com>, freebsd-hackers@freebsd.org Subject: Re: Mem leak : malloc/free + pthreads = leakage? Message-ID: <AANLkTimV2d0aYjeQp-OBeOwdhNjTkVfg7d9ATtc=t7SP@mail.gmail.com> In-Reply-To: <AANLkTiksK3RYkbVCj6wphOLu5oxvUNKWRrBOJb8VaGXp@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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Mar 6, 2011 at 10:34 AM, Ryan Stone <rysto32@gmail.com> wrote: > I would try playing with MALLOC_OPTIONS. =A0I 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. =A0The first thing I would try is setting MALLOC_OPTIONS=3D7h t= o > disable the caching. > Wait, sorry, apparently this is a new option in HEAD. Under 8.1 MALLOC_OPTIONS=3Dg will disable the thread-specific caching. See the malloc(3) man page for the definitive list of available options.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimV2d0aYjeQp-OBeOwdhNjTkVfg7d9ATtc=t7SP>