tree 7a74007609a3d19bc3009aa09a5eb7e83bba47eb
parent 749e67a947bc0183c90ba40f39ef95584f65ef9b
author Emircan Uysaler <uysalere@gmail.com> 1694620393 -0400
committer GitHub <noreply@github.com> 1694620393 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJlAdrpCRBK7hj4Ov3rIwAAHlYIABvk6QZj6kWOROX0vXSJoqMs
 jEcSkRNsXOIqnocFZBaQw5KKl0ovSlnbyt/dzM+eCRQ2o/zHJbraAf5tEqzbtwgr
 Na8vc440w/VQsDAshWyLA8eJ5WiBYg4xBNV6Zh4lMlpf04MflWW7mKS07DC/Fsqj
 30xSf8k6TeUGFN2s50c2BI5cjirtY6yQNe6wNfEg8hlE19tgtDKpcjuDolg0C1yZ
 xDGiera6xWshM0dn6NPfNENSouLafy03foi2cPJgAXZOzQ4sboRVsddcrOFAMZQh
 z8bH9toG1ciX3neGqF2ySPny9+BAt29L/oTMsgTPmzIGDo+qPfZrFtKKQiVX8Hs=
 =DOej
 -----END PGP SIGNATURE-----
 

[fuchsia] Restructure Flatland vsync loop (#45531) (#45712)

This CL restructures Flatland vsync loop to fire for each vsync instead
of each OnNextFrameBegin. As shown in the traces attached to the bug,
the current implementation of firing callbacks on each OnNextFrameBegin
causes skips when Flutter has longer draw calls. By scheduling frames in
between, we are increasing the chance of sending one before the latch
point. OnNextFrameBegin is now used to keep track of present credits and
future presentation times as well as when to start frame, replacing the
need for max_frames_in_flight and vsync_offset fields.

Bug: b/296272449
(cherry picked from commit
https://github.com/flutter/engine/commit/633ba427c498d9a5d096ac4979ecaa83ace4deaa)