Hi Gavriel.

Gavriel State wrote:
> Despite the workaround, we're still not too pleased with the current
> heap allocator.  It's quite slow, and still not as efficient as
> it could be.  It would probably be worth the effort to integrate
> a new allocator - anyone know if there's a high-quality Wine-license-
> compatible allocator out there?

I remember an analysis of various allocators which was done
for Mozilla.  This one came out very favourably (I think it
had the lowest fragmentation, for example) and it's also
public domain.

http://g.oswego.edu/dl/html/malloc.html


Reply via email to