GitLab

This patch fixes two issues that could previously lead to unterminated
LatencyInfo flows:
1) When we replace a surface (new surface for same frame sink
   activates) before frames on multiple old surfaces were activated or
   aggregated, we didn't correctly propagate the LatencyInfo from all
   old surfaces.
2) When a CompositorFrame is rejected by CompositorFrameSinkSupport
   or Surface::QueueFrame(), we should terminate its LatencyInfo, too.

Bug: 1056604
Change-Id: I1a4e2067cf1d762298cafb7fced6c7bbc9a7bd70
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2078015Reviewed-by: Jonathan Ross <jonross@chromium.org>
Commit-Queue: Eric Seckler <eseckler@chromium.org>
Cr-Commit-Position: refs/heads/master@{#747165}