
As a part of the existing Gpu Peak Memory Traces, we wish to also report the size of the differences. To make analysis easier. This updates GpuChannelManager::SequenceTracker to also track the initial state, and to use this when recording the traces. An example trace has been added to the tracking issue. TEST=GpuChannelManagerTest.GpuPeakMemoryOnlyReportedForValidSequence Bug: 1054256 Change-Id: I62855d76c897ff33bed2840d144727afba8aaabe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2115796 Commit-Queue: Jonathan Ross <jonross@chromium.org> Reviewed-by: Jonathan Ross <jonross@chromium.org> Reviewed-by: Jonathan Backer <backer@chromium.org> Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org> Cr-Commit-Position: refs/heads/master@{#754119}