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

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


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

android-nexus5x-perf

blink_perf.image_decoder - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

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

📍 Found significant differences after each of 7 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/16c2e6dd640000

Re-enable ARC IMEs that were auto-disabled when toggling to laptop mode by yusukes@chromium.org
https://chromium.googlesource.com/chromium/src/+/fcc50c50a5199456b025150012516b0f0e21a4ae
8716 → 8579 (-136.9)

Add M70 branch number. by wangge@google.com
https://chromium.googlesource.com/catapult/+/2834855ded52934a47ba1ca882cadea61515474d
8579 → 8689 (+109.3)

Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) by catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/fcfe9a6f17f02771890c03d666dcebf560eca909
8689 → 1.207e+04 (+3381)

Roll src/third_party/angle 9808d38c032a..0a17e484912d (1 commits) by angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/7973b34c5b24f1b8ea08536d8e8397e261fe15eb
1.196e+04 → 1.201e+04 (+47.81)

[ChromeDriver] Disable ChromeOptionsFunctionalTest by johnchen@chromium.org
https://chromium.googlesource.com/chromium/src/+/35893b77275d1bd4208bcb8596fb526790cefeb5
1.201e+04 → 1.203e+04 (+21.44)

WTF: Simplify ThreadCondition interface and make it more similar to base::ConditionVariable. by jbroman@chromium.org
https://chromium.googlesource.com/chromium/src/+/030ab478578929d75e79fad6f102d9d9eda107f6
1.203e+04 → 1.195e+04 (-78.14)

Use Element::LocalNameForSelectorMatching in InvalidationSet by fs@opera.com
https://chromium.googlesource.com/chromium/src/+/370b6a32ac4ed5b667b761ce0ad50a4092da0a03
1.197e+04 → 1.189e+04 (-83.38)

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

It looks like the catapult roll at r588413 caused a significant tick up (+3381), so that seems more likely.

Looking at the roll, I see https://chromium.googlesource.com/catapult.git/+/88dc49aaadb0d1295042023255f6bdceb706fa71 - which does seem relevant, and probably means this change is expected.