GitLab

The display compositor (viz) can skip over some frames for various
reasons, e.g. if the client is non-responsive, or if the gpu is busy
processing previous frames, etc. For these skipped frames, no
corresponding CompositorFrameReporter object is created. As a result,
there are no PipelineReporter trace events, which can make it confusing
when looking for dropped frames. To fix this, for every started frame,
create reporters for any earlier frames that were skipped over by viz.

BUG=1138086

Change-Id: I0b7f90de19d1148ccdb4e1877ee2e56e7ffad717
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2469777
Commit-Queue: Mingjing Zhang <mjzhang@chromium.org>
Reviewed-by: Mingjing Zhang <mjzhang@chromium.org>
Auto-Submit: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#817182}