GitLab

If a CompositorFrame is not produced in response to a begin-frame, then
it can be either because the compositor is attempting to recover from
high-latency, or because there was no update to the frame (i.e. there
was no damage). The latter cases should not cause the throughput metrics
to go down. This is currently handled for some cases (e.g. when the
main-frame is aborted due to no damage), but there are other cases where
the trackers are not notified, and thus they report lower throughput
metrics. To correct this, use the newly introduced FrameSkippedReason to
notify the trackers when a frame is not produced because there were no
damage.

BUG=1021963

Change-Id: I415e919738928c30322dd56cc67c23e4ebd73788
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1956567Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#723586}