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

Committed: https://crrev.com/ab408ac5e81ddf37772a9410cec2b7f747973a2d
Cr-Commit-Position: refs/heads/master@{#414765}

[enne (OOO), 2016-08-26 00:37:28]

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.

R=sievers@chromium.org
==========

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
==========

[enne (OOO), 2016-08-26 00:38:19]

The CQ bit was checked by enne@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-08-26 00:38:58]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-26 01:59:59]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-08-26 02:00:01]

Dry run: This issue passed the CQ dry run.

[no sievers, 2016-08-26 18:00:23]

lgtm

[enne (OOO), 2016-08-26 18:04:28]

The CQ bit was checked by enne@chromium.org

[commit-bot: I haz the power, 2016-08-26 18:05:23]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-26 18:52:58]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-08-26 19:16:30]

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
==========

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

Committed: https://crrev.com/ab408ac5e81ddf37772a9410cec2b7f747973a2d
Cr-Commit-Position: refs/heads/master@{#414765}
==========

[commit-bot: I haz the power, 2016-08-26 19:16:30]

Patchset 1 (id:??) landed as
https://crrev.com/ab408ac5e81ddf37772a9410cec2b7f747973a2d
Cr-Commit-Position: refs/heads/master@{#414765}