summaryrefslogtreecommitdiffstats
path: root/base
diff options
context:
space:
mode:
authorjar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-03-07 07:48:56 +0000
committerjar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-03-07 07:48:56 +0000
commit6dbb0f0658d3fd82bec3eea30c918f3a271a3f13 (patch)
tree439144889cc490b5959f3d8375a8fece5a800843 /base
parenta1943b06a28809e645020b3c3b271d12c1762572 (diff)
downloadchromium_src-6dbb0f0658d3fd82bec3eea30c918f3a271a3f13.zip
chromium_src-6dbb0f0658d3fd82bec3eea30c918f3a271a3f13.tar.gz
chromium_src-6dbb0f0658d3fd82bec3eea30c918f3a271a3f13.tar.bz2
Test performance of default allocator in browser process
This is a test, and will be reverted as soon as the build starts. We just want to see what the perf bots have to say. This CL changes the default allocator to be the Windows Allocator (rather than TCMalloc), but then overrides that default via the environment variable control *during* the running of the browser_main. The result is that the browser process will use the Windows Allocator, but all sub-processes, such as renderers, will use TCMalloc. TBR=cpu BUG=74901 Review URL: http://codereview.chromium.org/6624050 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77111 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base')
-rw-r--r--base/allocator/allocator_shim.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/base/allocator/allocator_shim.cc b/base/allocator/allocator_shim.cc
index 3935737..685f700 100644
--- a/base/allocator/allocator_shim.cc
+++ b/base/allocator/allocator_shim.cc
@@ -35,7 +35,7 @@ typedef enum {
} Allocator;
// This is the default allocator.
-static Allocator allocator = TCMALLOC;
+static Allocator allocator = WINDEFAULT;
// We include tcmalloc and the win_allocator to get as much inlining as
// possible.