Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(1451)

Unified Diff: cc/scheduler/scheduler.cc

Issue 1223403004: cc: Disable Renderer latency recovery with --disable-gpu-vsync (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@rendererLatencyRecoveryHeuristic13
Patch Set: Created 5 years, 5 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: cc/scheduler/scheduler.cc
diff --git a/cc/scheduler/scheduler.cc b/cc/scheduler/scheduler.cc
index 2b668e830114d89feb28844e8fc2a8030ae8a639..425266335707656becfbd24cd6e42ef697ce48a6 100644
--- a/cc/scheduler/scheduler.cc
+++ b/cc/scheduler/scheduler.cc
@@ -768,6 +768,12 @@ bool Scheduler::ShouldRecoverMainLatency(const BeginFrameArgs& args) const {
bool Scheduler::ShouldRecoverImplLatency(const BeginFrameArgs& args) const {
DCHECK(!settings_.using_synchronous_renderer_compositor);
+ // Disable impl thread latency recovery when using the unthrottled
+ // begin frame source since we will always get a BeginFrame before
+ // the swap ack and our heuristics below will not work.
+ if (!throttle_frame_production_)
+ return false;
+
// If we are swap throttled at the BeginFrame, that means the impl thread is
// very likely in a high latency mode.
bool impl_thread_is_likely_high_latency = state_machine_.SwapThrottled();
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698