Do we plan to switch the Mac build of Chromium to use tcmalloc instead
of the system malloc? I thought this was the case, but I can't find
any bug covering the task to do that. I'm on the memory task force,
and this decision could definitely have an impact (one direction or
the other) on footprint on Mac.
I just tried enabling tcmalloc (by changing USE_SYSTEM_MALLOC to 0 in
JavaScriptCore.gyp), and Chromium launches but logs a ton of warnings
about unknown pointers being freed.
I think this happens because tcmalloc is built by the 'wtf' target of
JavaScriptCore.xcodeproj, which is a static library, so we may be
ending up with multiple instances of the library with their own copies
of its globals, leading to this problem if one instance allocates a
block and another one tries to free it. But this usually happens only
if there are multiple dynamic libraries using the same static library
— do we have more than just Chromium.framework?
—Jens
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
