[Eraser] Remove chrome://tcmalloc

[Eraser] Remove chrome://tcmalloc

The chrome://tcmalloc page has been superseded by the memory-infra
category of chrome://tracing. The page no longer provides enough value
to justify its complexity in the codebase, so unlaunch it in the light
of Project Eraser.

Furthermore, this allows removing |base::allocator::GetStats|, which is
not used anywhere except in chrome:://tcmalloc. Detailed information
about memory allocators is available in the memory-infra category of
chrome://tracing. Unlike |GetStats|, which was implemented for tcmalloc
only, memory-infra provides detailed information about all allocators.

BUG=560250
Committed: https://crrev.com/f2ffd5e5b85a66d28f45e21d8d4cc2a221e80403
Cr-Commit-Position: refs/heads/master@{#361402}

[Ruud van Asseldonk, 2015-11-23 13:24:24]

ruuda@google.com changed reviewers:
+ jam@chromium.org, wfh@chromium.org

[Ruud van Asseldonk, 2015-11-23 13:24:24]

jam, wfh, can you please take a look at this cleanup CL?

[jam, 2015-11-23 17:00:31]

lgtm

[Primiano Tucci (use gerrit), 2015-11-24 10:18:02]

primiano@chromium.org changed reviewers:
+ primiano@chromium.org

[Primiano Tucci (use gerrit), 2015-11-24 10:18:03]

LGTM but you missed to remove one IPC message.

https://codereview.chromium.org/1468993003/diff/1/content/common/child_proces...
File content/common/child_process_messages.h (right):

https://codereview.chromium.org/1468993003/diff/1/content/common/child_proces...
content/common/child_process_messages.h:194:
IPC_MESSAGE_CONTROL1(ChildProcessHostMsg_TcmallocStats,
I think you want to remove this as well.

[Ruud van Asseldonk, 2015-11-24 11:10:37]

https://codereview.chromium.org/1468993003/diff/1/content/common/child_proces...
File content/common/child_process_messages.h (right):

https://codereview.chromium.org/1468993003/diff/1/content/common/child_proces...
content/common/child_process_messages.h:194:
IPC_MESSAGE_CONTROL1(ChildProcessHostMsg_TcmallocStats,
On 2015/11/24 10:18:03, Primiano Tucci wrote:
> I think you want to remove this as well.

Done, good catch.

[Will Harris, 2015-11-24 18:23:34]

lgtm but sounds like you already have reviewer coverage.

[Primiano Tucci (use gerrit), 2015-11-24 18:27:55]

On 2015/11/24 18:23:34, Will Harris wrote:
> lgtm but sounds like you already have reviewer coverage.

Nope, you are unique and irrepetible when it comes to *_message.h ;-)

from content/common/OWNERS
per-file *_message*.h=set noparent
...
per-file *_message*.h=wfh@chromium.org

[Ruud van Asseldonk, 2015-11-24 18:38:42]

The CQ bit was checked by ruuda@google.com

[Ruud van Asseldonk, 2015-11-24 18:38:42]

The patchset sent to the CQ was uploaded after l-g-t-m from
primiano@chromium.org, jam@chromium.org
Link to the patchset: https://codereview.chromium.org/1468993003/#ps40001
(title: "Address primiano comment, remove declaration from gpu_child_thread")

[commit-bot: I haz the power, 2015-11-24 18:39:30]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1468993003/40001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1468993003/40001

[commit-bot: I haz the power, 2015-11-24 18:50:00]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-11-24 18:51:18]

Patchset 3 (id:??) landed as
https://crrev.com/f2ffd5e5b85a66d28f45e21d8d4cc2a221e80403
Cr-Commit-Position: refs/heads/master@{#361402}