<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On Sep 4, 2014, at 9:14 AM, David Rigby <<a href="mailto:daver@couchbase.com">daver@couchbase.com</a>> wrote:<div><blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div>I’m having some problems using je_malloc_conf to configure jemalloc’s runtime behaviour, but *only on OSX* - Linux is fine. The behaviour I see is that any je_malloc_conf setting on OS X Mavericks (clang-503.0.40) is ignored, but works perfectly when compiling
on Ubuntu 14.04, x86_64, gcc 4.8.2)</div>
<div><br>
</div>
<div>I’m defining je_malloc_conf as:</div>
<div><br>
</div>
<div> const char* je_malloc_conf = "narenas:1";<br>
<br>
</div>
<div>[...]</div>
</div></blockquote></div><div><br></div>It turns out that this doesn't work on FreeBSD anymore either, and I'm certain that it used to. My guess is that something changed with regard to duplicate symbol resolution that requires jemalloc to declare its malloc_conf definition as a weak symbol, but I haven't had a chance to investigate yet. Here's the issue I just created:<div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://github.com/jemalloc/jemalloc/issues/113">https://github.com/jemalloc/jemalloc/issues/113</a></div><div><br></div><div>If you learn more, or come up with a fix, please let me know.</div><div><br></div><div>Thanks,</div><div>Jason</div></body></html>