Revert of Turn on enable begin frame scheduling by default

Revert of Turn on enable begin frame scheduling by default (patchset #11 id:200001 of https://codereview.chromium.org/1939253002/ )

Reason for revert:
Causes smoothness regressions, other bugs

BUG=623174, 623467, 623490
Original issue's description:
> Turn on enable begin frame scheduling by default
>
> This turns on --enable-begin-frame-scheduling[1] for all[2] platforms.
> This was already on for Android so should only be a real change
> for desktop / ChromeOS platforms.
>
> Lots of cleanup can follow from this like removing all commit vsync /
> authoritative vsync / CompositorVSyncManager things, but this is a
> smaller patch to suss out any performance regressions.
>
> [1] In this case, "begin frame scheduling" means browser->renderer
> begin frame ticks instead of sending vsync information and having
> a synthetic source on the renderer side.
>
> [2] MUS is not hooked up to begin frame scheduling yet, but
> mojo:mash_session in an "oxygen" build still works with this patch
> applied.  Blimp also doesn't use begin frame scheduling and will
> eventually just be transitioned to a synthetic begin frame source
> for its engine half.
>
> CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
>
> Committed: https://crrev.com/f2d7f5e1891703ec4384ededd80f896816921204
> Cr-Commit-Position: refs/heads/master@{#401796}

TBR=boliu@chromium.org,piman@chromium.org,skyostil@chromium.org,sunnyps@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.

Committed: https://crrev.com/7ea3a9cd847d7478598d22804d04c32c156c14f4
Cr-Commit-Position: refs/heads/master@{#402294}

[enne (OOO), 2016-06-27 18:23:47]

The CQ bit was checked by enne@chromium.org

[enne (OOO), 2016-06-27 18:23:47]

Created Revert of Turn on enable begin frame scheduling by default

[commit-bot: I haz the power, 2016-06-27 18:24:17]

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-06-27 19:17:34]

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

[commit-bot: I haz the power, 2016-06-27 19:17:35]

Try jobs failed on following builders:
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[enne (OOO), 2016-06-27 19:45:49]

The CQ bit was checked by enne@chromium.org

[commit-bot: I haz the power, 2016-06-27 19:47:08]

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-06-27 21:38:58]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-27 21:40:43]

Description was changed from

==========
Revert of Turn on enable begin frame scheduling by default (patchset #11
id:200001 of https://codereview.chromium.org/1939253002/ )

Reason for revert:
Causes smoothness regressions, other bugs

BUG=623174,623467,623490

Original issue's description:
> Turn on enable begin frame scheduling by default
> 
> This turns on --enable-begin-frame-scheduling[1] for all[2] platforms.
> This was already on for Android so should only be a real change
> for desktop / ChromeOS platforms.
> 
> Lots of cleanup can follow from this like removing all commit vsync /
> authoritative vsync / CompositorVSyncManager things, but this is a
> smaller patch to suss out any performance regressions.
> 
> [1] In this case, "begin frame scheduling" means browser->renderer
> begin frame ticks instead of sending vsync information and having
> a synthetic source on the renderer side.
> 
> [2] MUS is not hooked up to begin frame scheduling yet, but
> mojo:mash_session in an "oxygen" build still works with this patch
> applied.  Blimp also doesn't use begin frame scheduling and will
> eventually just be transitioned to a synthetic begin frame source
> for its engine half.
> 
> CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
> 
> Committed: https://crrev.com/f2d7f5e1891703ec4384ededd80f896816921204
> Cr-Commit-Position: refs/heads/master@{#401796}

TBR=boliu@chromium.org,piman@chromium.org,skyostil@chromium.org,sunnyps@chrom...
# Not skipping CQ checks because original CL landed more than 1 days ago.
==========

to

==========
Revert of Turn on enable begin frame scheduling by default (patchset #11
id:200001 of https://codereview.chromium.org/1939253002/ )

Reason for revert:
Causes smoothness regressions, other bugs

BUG=623174,623467,623490

Original issue's description:
> Turn on enable begin frame scheduling by default
>
> This turns on --enable-begin-frame-scheduling[1] for all[2] platforms.
> This was already on for Android so should only be a real change
> for desktop / ChromeOS platforms.
>
> Lots of cleanup can follow from this like removing all commit vsync /
> authoritative vsync / CompositorVSyncManager things, but this is a
> smaller patch to suss out any performance regressions.
>
> [1] In this case, "begin frame scheduling" means browser->renderer
> begin frame ticks instead of sending vsync information and having
> a synthetic source on the renderer side.
>
> [2] MUS is not hooked up to begin frame scheduling yet, but
> mojo:mash_session in an "oxygen" build still works with this patch
> applied.  Blimp also doesn't use begin frame scheduling and will
> eventually just be transitioned to a synthetic begin frame source
> for its engine half.
>
> CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
>
> Committed: https://crrev.com/f2d7f5e1891703ec4384ededd80f896816921204
> Cr-Commit-Position: refs/heads/master@{#401796}

TBR=boliu@chromium.org,piman@chromium.org,skyostil@chromium.org,sunnyps@chrom...
# Not skipping CQ checks because original CL landed more than 1 days ago.

Committed: https://crrev.com/7ea3a9cd847d7478598d22804d04c32c156c14f4
Cr-Commit-Position: refs/heads/master@{#402294}
==========

[commit-bot: I haz the power, 2016-06-27 21:40:45]

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