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

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


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

Android Nexus5 Perf
Win 7 Perf
mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_end-perf

memory.desktop - Benchmark documentation link:
  None

system_health.memory_mobile - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

memory.top_10_mobile - Benchmark documentation link:
  None

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

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

Scheduler: WebURLLoader should notify Blink with the initial priority. by farahcharab@google.com
https://chromium.googlesource.com/chromium/src/+/d2bade563869c5a429d129695ce754ca0f5e9507
3.568e+07 → 3.798e+07 (+2.303e+06)

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

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

Reran bisect.

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

Deadline exceeded while waiting for HTTP response from URL: https://chromium.googlesource.com/chromium/src/+log/4d18295073a6bf8f2f4d26e4e059767e091eaaf3..bf2c7f57a69dc8b80cb107ff613717a007a19ecd?format=JSON

The bug is too old to be actionable now.  I spot-checked a few metrics involved here, they seem to have mostly recovered in the last few months.