Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
Information redacted by Android Beta Feedback.
na...@google.com <na...@google.com> #3
Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
Description
Macrobenchmark FrameTimingMetric makes a couple assumptions that I'm not seeing hold true on the trace above:
actual <nr>
expected <nr>
Choreographer#doFrame <nr>
DrawFrame <nr>
Note: we observe instead that frame numbers for actual/expected get out of sync, see screenshot.
Note: we observe instead that the actual frame is wrapping a separate renderthread render
The problem
Together, these mean that macrobenchmarks drop many frames, and don't report them as part of metrics. In this scenario (MotionLayoutBenchmark#messageJson), it's roughly ~100 frames dropped out of ~140.
See also b/210605870