diff options
| author | jar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-03-06 08:02:54 +0000 |
|---|---|---|
| committer | jar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-03-06 08:02:54 +0000 |
| commit | a7e4016e7eb30d8056e1e65e2888de36a15a0f4f (patch) | |
| tree | da4240fee88c724dc55cb8f7f0035d95945fd273 /tools/grit/resource_ids | |
| parent | 656643743582980d046f757590e20a48ec9e4bfb (diff) | |
| download | chromium_src-a7e4016e7eb30d8056e1e65e2888de36a15a0f4f.zip chromium_src-a7e4016e7eb30d8056e1e65e2888de36a15a0f4f.tar.gz chromium_src-a7e4016e7eb30d8056e1e65e2888de36a15a0f4f.tar.bz2 | |
Revert 77066 - Test impact of using default windows allocator
I'll revert this as soon as the builds kick off.
I just want to look at perf impact.
I'll ceate a fancier CL that uses different allocators
for render vs browser, but I wanted an overall baseline
for transitioning completely from TCMalloc to
the default allocator on Windows.
TBR=cpu
Review URL: http://codereview.chromium.org/6635004
TBR=jar@chromium.org
Review URL: http://codereview.chromium.org/6623041
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77067 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools/grit/resource_ids')
0 files changed, 0 insertions, 0 deletions