Re: Using new jemalloc features in our code

Sergey Yanovich wrote:

> It is right now (with --disable-jemalloc). However, Benjamin wrote in 
> the proposal at the root of this thread in m.d.platform:
> 
>> My proposed solution to this problem is as follows:
>>
>> * Always build jemalloc. Mozilla code should not use malloc()/free(), 
>> but mozilla-specific symbol names such as NS_Alloc() or JE_malloc()
>>
>> * where possible, hook jemalloc into the CRT so that it allocates all 
>> malloc()ed memory and there is a unified heap
> 
> This seems to imply making --disable-jemalloc obsolete, which is why I 
> am raising the legal issue under discussion.

I think you misunderstood the proposal. It requires that we always build 
jemalloc. It does *not* require that we always build jemalloc *into the 
CRT*. For those without MSVC professional, or who are bound by the GPL, 
jemalloc would be a mozilla library, e.g. libmozjemalloc.so or somesuch.

--BDS