DescriptionRevert of Implement scroll handler latency tracking (https://codereview.chromium.org/365463003/)
Reason for revert:
Breaks smoothness benchmarks on windows:
"ValueError: LatencyInfo has no begin component"
http://chromegw/i/chromium.perf/builders/Win%207%20Intel%20GPU%20Perf/builds/16918/steps/smoothness.top_25/logs/stdio
TBR=rschoen@chromium.org
Original issue's description:
> Implement scroll handler latency tracking
>
> Since scroll handlers do not block composited scrolling, the existing
> input latency metric will only report the response time for the
> compositor when scrolling a page with a handler. This is not accurate
> for pages that implement scroll-synchronized effects, because the
> scroll handler needs to be invoked so that the page contents are
> updated with the new scroll offset.
>
> This patch fixes the problem by forwarding latency information from the
> impl to the main thread when we are scrolling a layer that has an active
> scroll event handler.
>
> In the case the scroll handler is no-op, the latency information will be
> terminated as a failed commit.
>
> Sample trace:
> https://drive.google.com/file/d/0ByyxMXB38gLDRE40bkU5TVd0U00/edit?usp=sharing
>
> BUG=347366
>
> Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=282117
>
> Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=287325
Patch Set 1 #
Created: 6 years, 4 months ago
(Patch set is too large to download)
Messages
Total messages: 11 (1 generated)
|