diff options
| author | jar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-03-06 07:54:27 +0000 |
|---|---|---|
| committer | jar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-03-06 07:54:27 +0000 |
| commit | 656643743582980d046f757590e20a48ec9e4bfb (patch) | |
| tree | b79919410aa9ba3d700399f0a0ecb35295f8a06b /tools/grit/resource_ids | |
| parent | 847eea0f71d2beda35095fc8e10436728d76821b (diff) | |
| download | chromium_src-656643743582980d046f757590e20a48ec9e4bfb.zip chromium_src-656643743582980d046f757590e20a48ec9e4bfb.tar.gz chromium_src-656643743582980d046f757590e20a48ec9e4bfb.tar.bz2 | |
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
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@77066 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools/grit/resource_ids')
0 files changed, 0 insertions, 0 deletions