Since Noncopyable'll be inherited from FastAllocBase (and RefCounted has been inherited from Noncopyable), in case of DRT classes using of TCmalloc must be avoided. This change repairs the GTK+'s DRT build fail as well (in case of inheriting Noncopyable from FastAllocBase bug #27879).
Created attachment 34266 [details] proposed patch
Comment on attachment 34266 [details] proposed patch This makes the class name RefCountedCustomAllocated seem pretty bad. After all, there's no desire to "custom allocate" here. I think we should consider doing this with the preprocessor instead of different class names when we're talking about an entirely different binary like DumpRenderTree, since USE_SYSTEM_MALLOC is already set. Can we investigate that instead?
Why are we trying to avoid using FastMalloc from DumpRenderTree? DRT's config.h explicitly includes FastMalloc.h so that uses of operator new will go via fastMalloc.
GTK+ guys solved the build error in r46944 (http://trac.webkit.org/changeset/46944/trunk/WebKitTools/GNUmakefile.am) which caused by Noncopyable's change, so this patch is obsolete.