viz: Add a flag to do double-buffering compositing
Chrome on ChromeOS uses triple buffering by default, keeping up to 2
buffers in flight while one is displayed.
This CL adds a flag in chrome://flags that limits to 1 the number of
pending frames, effectively reducing compositing to double-buffering.
This can be useful for experimenting on devices where we want to
minimize latency at the cost of more dropped frames.
Bug: 1010457
Change-Id: I0cddb4c1831d5b909ee3c0193d42f3903e10d03a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2059709
Commit-Queue: Daniele Castagna <[email protected]>
Reviewed-by: Miguel Casas <[email protected]>
Reviewed-by: Nico Weber <[email protected]>
Reviewed-by: Andres Calderon Jaramillo <[email protected]>
Cr-Commit-Position: refs/heads/master@{#742351}
diff --git a/chrome/browser/flag_descriptions.h b/chrome/browser/flag_descriptions.h
index 0c6bccd..b92a3f2c 100644
--- a/chrome/browser/flag_descriptions.h
+++ b/chrome/browser/flag_descriptions.h
@@ -190,6 +190,9 @@
extern const char kDecodeLossyWebPImagesToYUVName[];
extern const char kDecodeLossyWebPImagesToYUVDescription[];
+extern const char kDoubleBufferCompositingName[];
+extern const char kDoubleBufferCompositingDescription[];
+
extern const char kDnsOverHttpsName[];
extern const char kDnsOverHttpsDescription[];
