Add chrome://flags entry for bloated renderer detection
- Adds chrome://flags entry
- Adds a FeatureFlag
- Make existing Blink flag dependent on the Chrome flag
Bug: 808143
Change-Id: Ib48328a63cda8007cf863741cae92957757538e2
Reviewed-on: https://chromium-review.googlesource.com/1140328
Commit-Queue: Ulan Degenbaev <[email protected]>
Reviewed-by: Jochen Eisinger <[email protected]>
Reviewed-by: Michael Lippautz <[email protected]>
Cr-Commit-Position: refs/heads/master@{#576455}diff --git a/chrome/browser/about_flags.cc b/chrome/browser/about_flags.cc
index efc618d4..1f7d855 100644
--- a/chrome/browser/about_flags.cc
+++ b/chrome/browser/about_flags.cc
@@ -4113,6 +4113,11 @@
FEATURE_VALUE_TYPE(app_list::features::kEnableContinueReading)},
#endif // OS_CHROMEOS
+ {"enable-bloated-renderer-detection",
+ flag_descriptions::kEnableBloatedRendererDetectionName,
+ flag_descriptions::kEnableBloatedRendererDetectionDescription, kOsAll,
+ FEATURE_VALUE_TYPE(features::kBloatedRendererDetection)},
+
// NOTE: Adding a new flag requires adding a corresponding entry to enum
// "LoginCustomFlags" in tools/metrics/histograms/enums.xml. See "Flag
// Histograms" in tools/metrics/histograms/README.md (run the
