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

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


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

Android Nexus5 Perf
android-nexus5x-perf

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

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

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

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

📍 Found significant differences after each of 6 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/11c6b8b9640000

Revert "Android: Update version of retrace.jar to 6.0.3" by agrieve@chromium.org
https://chromium.googlesource.com/chromium/src/+/78561f5b9dca2d5e742a43ddf0f553eaf4a76c70
0.1967 → No values

Add image_fetcher::IOSImageDataFetcherWrapper to ImageFetchTabHelper by mrsuyi@google.com
https://chromium.googlesource.com/chromium/src/+/378627db2f935cd7ecde04736fea77f41e0e2e2b
No values → 0.1955

Fix path to CMake bin directory in update.py by rnk@google.com
https://chromium.googlesource.com/chromium/src/+/536bb7d3cf643f606bc91678a1fcaf4077f76f99
0.1938 → No values

[Chromecast] Upload all crashes to main crash server by servolk@google.com
https://chromium.googlesource.com/chromium/src/+/9808d454ddcdf6124e258fe3323b71dcabd25f60
No values → 0.1938

Add back tight scaler context managment by herb@google.com
https://skia.googlesource.com/skia/+/ee2a3f36dcf7fbd4db664f93a08c095a8a76b20b
0.1937 → 0.2014 (+0.007672)

Have GPU and RemoteGlyphCache share mask position code by herb@google.com
https://skia.googlesource.com/skia/+/d2fec23523bcdd796840725a64d4c40b5fcec215
0.2002 → 0.2161 (+0.0159)

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

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/103b591b640000

The swarming task expired. The bots are likely overloaded, dead, or misconfigured.

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

Scheduler: WebURLLoader should notify Blink with the initial priority. by farahcharab@google.com
https://chromium.googlesource.com/chromium/src/+/d2bade563869c5a429d129695ce754ca0f5e9507
38.5 → 302.1 (+263.6)

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

This looks like an omnibus bug. Both the bugs "Add back tight scaler context managment" and "Have GPU and RemoteGlyphCache share mask position" are for correctness. The first fixes regressive behavior in memory usage, and the second makes the code between the Renderer and the GPU communicate correctly.

Removing my name so that the regression in the CL "WebURLLoader should notify Blink with the initial priority" can be tracked.