[Webkit-unassigned] [Bug 103027] [Chromium] fastMalloc has an extra branch on Windows

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=103027





--- Comment #8 from Adam Barth <abarth at webkit.org>  2012-11-22 22:27:24 PST ---
To answer your questions...

> I'm not sure of the terminology you're using (global vs per-object new).

These are WebKit-specific overrides in http://trac.webkit.org/browser/trunk/Source/WTF/wtf/FastMalloc.h#L259 and http://trac.webkit.org/browser/trunk/Source/WTF/wtf/FastAllocBase.h#L96

> On Mac Chrome we override the world when it comes to allocators, probably redundantly.

In bug 102866, we observe a speedup by switch to using WebKit's copy of TCMalloc instead of defining the USE(SYSTEM_MALLOC) symbol.  Based on profiles and looking at symbols, it appears that currently on Mac, WebKit uses the OS-provided malloc implementation, which isn't particularly fast.

Is process_util_mac.mm supposed to cause WebKit to use a malloc implementation other than the system-provided implementation?  (Please feel free to respond on bug 102866 as that bug is actually about Mac.)

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.