android: Use a hard coded BeginFrame deadline
commitb91af0d2b8ff9072a376b1a8c8ebd108d536c056
authorbrianderson <brianderson@chromium.org>
Thu, 16 Jul 2015 20:46:40 +0000 (16 13:46 -0700)
committerCommit bot <commit-bot@chromium.org>
Thu, 16 Jul 2015 20:47:16 +0000 (16 20:47 +0000)
tree94d3eba94d715a0a1fc3c5d5fa5e65a1ad020b32
parent6414e43520905218aee5a6e9d5a2914199abd104
android: Use a hard coded BeginFrame deadline

The previous estimation logic measures the time from when the
Browser receives the Renderer swap to when the Browser swaps,
which may include idle time when the Renderer is in a high
latency mode.

This often prevented us from detecting that we can recover
that latency.

The correct estimation logic will look completely different for
Surfaces vs. Android's current path; so the plan is to use a
hard coded for now and use estimation logic again once
Surfaces come to Android.

BUG=510623

Review URL: https://codereview.chromium.org/1244443003

Cr-Commit-Position: refs/heads/master@{#339114}
content/browser/renderer_host/input/render_widget_host_latency_tracker.cc
content/browser/renderer_host/input/render_widget_host_latency_tracker.h
content/browser/renderer_host/render_widget_host_impl.cc
content/browser/renderer_host/render_widget_host_impl.h
content/browser/renderer_host/render_widget_host_view_android.cc