Re: Using new jemalloc features in our code

Gervase Markham wrote:
> Sergey Yanovich wrote:
>> Firefox 3.0 on Windows already ships jemalloc patched MS CRT.
> 
> Is it possible to build Firefox without this, or is it required?

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.

-- 
Sergey Yanovich