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

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


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

mac-10_13_laptop_high_end-perf

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

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

📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/14c3e94a540000

[omnibox] Condition accessibility call by krb@chromium.org
https://chromium.googlesource.com/chromium/src/+/33c72e13ece49c36938905cb6d87fbf15e9a0cfb
timeToFirstPaint: 390.6 → 340 (-50.62)

[mojo] Per-message dispatch tasks by rockot@google.com
https://chromium.googlesource.com/chromium/src/+/471aa794bbb9e3a98542ee2135ea61ddf4bf87a3
timeToFirstPaint: 355.1 → 586.9 (+231.8)

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

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