Move frame eviction into components

components/display_compositor/display_compositor_features.cc

Index: components/display_compositor/display_compositor_features.cc
diff --git a/components/display_compositor/display_compositor_features.cc b/components/display_compositor/display_compositor_features.cc
new file mode 100644
index 0000000000000000000000000000000000000000..61c995d1255cd0510e9a9e525a88f506ff1198c9
--- /dev/null
+++ b/components/display_compositor/display_compositor_features.cc
@@ -0,0 +1,20 @@
+// Copyright 2017 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#include "components/display_compositor/display_compositor_features.h"
+
+namespace display_compositor {
+
+namespace features {
+
+// Enables the memory coordinator.
+// WARNING:
+// The memory coordinator is not ready for use and enabling this may cause
+// unexpected memory regression at this point. Please do not enable this.
+const base::Feature kMemoryCoordinator{"MemoryCoordinator",

[Saman Sami, 2017/04/11 14:58:24]

I wonder if this works properly? So if the feature in content is on, is this one
on too?

[boliu, 2017/04/11 15:37:29]

The real problem here is that this is an implicit dependency on content, since
MemoryCoordinator is a content feature.

[xing.xu, 2017/04/14 03:01:29]

Done.

[xing.xu, 2017/04/14 03:01:29]

Done.

+                                       base::FEATURE_DISABLED_BY_DEFAULT};
+
+}  // namespace features
+
+}  // namespace display_compositor