Fix jank on Android due to bad scheduler deadline

Fix jank on Android due to bad scheduler deadline

https://codereview.chromium.org/1821863002 changed the display scheduler
on Android to use the CompositorImpl ExternalBeginFrameSource directly
instead of a synthetic BeginFrameSource that had its vsync parameters
set from WindowAndroidCompositor::OnVSync.

The frame time given to the display scheduler is always in the past,
which made the past logic always give an immediate deadline, causing
the display scheduler to run immediately.  Fix this by providing a
correct deadline in the future.

This fixes bad jank where the display scheduler would never give any
other compositors time to give frames.  So, if the browser compositor
was producing frames (such as a loading spinner) then the renderer
frames would be extremely janky as they would often miss the immediate
(incorrect) deadline.

BUG=613193
R=sievers@chromium.org

Review-Url: https://codereview.chromium.org/2275253003
Cr-Commit-Position: refs/heads/master@{#414765}
(cherry picked from commit ab408ac5e81ddf37772a9410cec2b7f747973a2d)

Committed: https://chromium.googlesource.com/chromium/src/+/1194983de5b5fb8ec58bbe47e3574bc95048fc50

[enne (OOO), 2016-08-30 20:16:01]

Description was changed from

==========
Fix jank on Android due to bad scheduler deadline

https://codereview.chromium.org/1821863002 changed the display scheduler
on Android to use the CompositorImpl ExternalBeginFrameSource directly
instead of a synthetic BeginFrameSource that had its vsync parameters
set from WindowAndroidCompositor::OnVSync.

The frame time given to the display scheduler is always in the past,
which made the past logic always give an immediate deadline, causing
the display scheduler to run immediately.  Fix this by providing a
correct deadline in the future.

This fixes bad jank where the display scheduler would never give any
other compositors time to give frames.  So, if the browser compositor
was producing frames (such as a loading spinner) then the renderer
frames would be extremely janky as they would often miss the immediate
(incorrect) deadline.

BUG=613193
R=sievers@chromium.org

Review-Url: https://codereview.chromium.org/2275253003
Cr-Commit-Position: refs/heads/master@{#414765}
(cherry picked from commit ab408ac5e81ddf37772a9410cec2b7f747973a2d)
==========

to

==========
Fix jank on Android due to bad scheduler deadline

https://codereview.chromium.org/1821863002 changed the display scheduler
on Android to use the CompositorImpl ExternalBeginFrameSource directly
instead of a synthetic BeginFrameSource that had its vsync parameters
set from WindowAndroidCompositor::OnVSync.

The frame time given to the display scheduler is always in the past,
which made the past logic always give an immediate deadline, causing
the display scheduler to run immediately.  Fix this by providing a
correct deadline in the future.

This fixes bad jank where the display scheduler would never give any
other compositors time to give frames.  So, if the browser compositor
was producing frames (such as a loading spinner) then the renderer
frames would be extremely janky as they would often miss the immediate
(incorrect) deadline.

BUG=613193
R=sievers@chromium.org

Review-Url: https://codereview.chromium.org/2275253003
Cr-Commit-Position: refs/heads/master@{#414765}
(cherry picked from commit ab408ac5e81ddf37772a9410cec2b7f747973a2d)

Committed:
https://chromium.googlesource.com/chromium/src/+/1194983de5b5fb8ec58bbe47e357...
==========

[enne (OOO), 2016-08-30 20:16:04]

Committed patchset #1 (id:1) manually as
1194983de5b5fb8ec58bbe47e3574bc95048fc50.