[PM] Adding a working set trimmer policy.
As discussed this CL will add a WorkingSetTrimmer policy. The default
policy as implemented in working_set_trimmer_policy is identical to the
previous behavior on Windows in which we will always trim on frozen.
The Windows implementation uses that same default behavior but uses
PlatformSupportsWorkingSetTrim to check if it's flag enabled.
The ChromeOS implementation uses the same default plus it adds working
set trim on Moderate memory pressure. There are a number of flags used
to control this behavior.
Bug: 973963
Change-Id: I2dfd4a8e7e45497725cb905bc1254beb8fda3ae3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1706450
Commit-Queue: Brian Geffon <[email protected]>
Reviewed-by: Marc Treib <[email protected]>
Reviewed-by: Chris Hamilton <[email protected]>
Cr-Commit-Position: refs/heads/master@{#682475}
diff --git a/chrome/browser/flag_descriptions.h b/chrome/browser/flag_descriptions.h
index e9bd0de..649fa49 100644
--- a/chrome/browser/flag_descriptions.h
+++ b/chrome/browser/flag_descriptions.h
@@ -1924,6 +1924,12 @@
extern const char kEnableVirtualDesksName[];
extern const char kEnableVirtualDesksDescription[];
+extern const char kTrimOnFreezeName[];
+extern const char kTrimOnFreezeDescription[];
+
+extern const char kTrimOnMemoryPressureName[];
+extern const char kTrimOnMemoryPressureDescription[];
+
extern const char kEnableZeroStateSuggestionsName[];
extern const char kEnableZeroStateSuggestionsDescription[];
