tree e18b7d156edf50a9a5c604cc176a58e8fd8e8448
parent a9fc6c03df9a9f24a51127e97d8e291b966c50bc
author Sigurdur Asgeirsson <siggi@chromium.org> 1551972115 +0000
committer Commit Bot <commit-bot@chromium.org> 1551972115 +0000

PM: Only enable instrumentation under the chrome embedder.

As of https://chromium-review.googlesource.com/c/1425042, content/
no longer provides forwarding for the ResourceCoordinator
instrumentation interfaces. This was a step in a larger refactoring,
but had the effect of orphaning the instrumentation in all but the
chrome/browser embedder. This in turn led to a memory regression in
the Android WebView.
This CL makes the initialization and the usage of the instrumentation
interfaces conditional on a runtime flag, which is only set by the
ChromeContentRendererClient.
This is still an intermediate state in the refactoring, as the
interfaces in question will be moved and simplified.

Bug: 926426
Change-Id: Ia640f544b536bf86d53e853de6178aeaf9c9b6f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1496303
Commit-Queue: Sigurður Ásgeirsson <siggi@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Stephen White <senorblanco@chromium.org>
Reviewed-by: Chris Hamilton <chrisha@chromium.org>
Cr-Commit-Position: refs/heads/master@{#638575}