Date: Sun, 6 Mar 2011 10:34:11 -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: <AANLkTiksK3RYkbVCj6wphOLu5oxvUNKWRrBOJb8VaGXp@mail.gmail.com> In-Reply-To: <AANLkTi=K9QuK%2BbyxF1t7HzG9wKxXek804tNOgzM3Dp_b@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTiksK3RYkbVCj6wphOLu5oxvUNKWRrBOJb8VaGXp>