All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=883758

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=72cf201a56710e3e2ae09bb64c98b2276045994ddc84c3d329d7158979e7e629


Bot(s) for this bug's original alert(s):

android-nexus5x-perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/16344055640000

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/16344055640000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/1207c1e3640000

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/1207c1e3640000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/101d6179640000

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/101d6179640000

Revert "Use GL_COMMANDS_ISSUED_CHROMIUM query for shared memory GpuMemoryBuffers" by ericrk@chromium.org
https://chromium.googlesource.com/chromium/src/+/6eb9eee331affe92c52a2926f57422bcbf40fa43
10.5 → 11.04 (+0.5409)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

This was a revert of a performance optimization due to correctness issues. It would be nice to re-land the optimization, and we will if possible, but this is not a real regression as the optimization was only in place for a couple days.