Comment #10 on issue 27911 by [email protected]: TCMalloc needs to be forked in order to compile correctly http://code.google.com/p/chromium/issues/detail?id=27911
@antonm To the extent to which we can maintain our choice of a multitude of allocators without that much work, I think it is a big win. It will allow us to vary allocators, which in turn may expose different bugs, as different heap-monitoring tools are employed. Also, different allocation strategies result in vastly different memory layout which in turn may instigate different bugs. IMO, it is interesting (for example) to do some stability tests with different allocators. At different times historically, folks have asked what the impact of using the Windows Low Fragmentation Heap, or JEMalloc. Having the switchable infrastrucuter helped us answer this in the past, and will help us again answer this in the future as newer and/or improved-versions of allocators appear on the scene. Is there a large cost that I'm not seeing? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
