summaryrefslogtreecommitdiffstats
path: root/content/content_common.gypi
diff options
context:
space:
mode:
authorprimiano <primiano@chromium.org>2016-01-25 11:43:44 -0800
committerCommit bot <commit-bot@chromium.org>2016-01-25 19:53:50 +0000
commitbdcad645c59f39bb4ccb72f04ebdd0ab1e2bf75d (patch)
tree2656fbf9c153c26b704a254d1c3cb18e9d1285e8 /content/content_common.gypi
parent55c4a3dd76678fded67f141e5853343762f9b5de (diff)
downloadchromium_src-bdcad645c59f39bb4ccb72f04ebdd0ab1e2bf75d.zip
chromium_src-bdcad645c59f39bb4ccb72f04ebdd0ab1e2bf75d.tar.gz
chromium_src-bdcad645c59f39bb4ccb72f04ebdd0ab1e2bf75d.tar.bz2
allocator cleanup: remove memory benchmarking extension
The memory benchmarking extension, introduced in crrev.com/12211008 allows to expose the TCMalloc heap profiler methods to JS by passing a command line flag. These days there doesn't seem to be any client left anywhere in the codebase. See also the thread: [chromium-dev] Is anybody using/caring about --enable-memory-benchmarking The command line switch itself is deliberately not removed as it still relied on for crbug.com/513692 BUG=564618 Review URL: https://codereview.chromium.org/1610213002 Cr-Commit-Position: refs/heads/master@{#371285}
Diffstat (limited to 'content/content_common.gypi')
-rw-r--r--content/content_common.gypi1
1 files changed, 0 insertions, 1 deletions
diff --git a/content/content_common.gypi b/content/content_common.gypi
index e4d0884..07af871 100644
--- a/content/content_common.gypi
+++ b/content/content_common.gypi
@@ -445,7 +445,6 @@
'common/media/video_capture.h',
'common/media/video_capture_messages.h',
'common/media/webrtc_identity_messages.h',
- 'common/memory_benchmark_messages.h',
'common/memory_messages.h',
'common/message_port_messages.h',
'common/message_router.cc',