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

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


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/13c96daee40000

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

Roll AFDO from 72.0.3582.0_rc-r1 to 72.0.3583.0_rc-r1 by chromium-autoroll@skia-public.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/a630a996c84d410a7a27a6a8e80f95da4cc68b36
decode-lossless-webp: 1.22e+04 → 1.261e+04 (+414.8)

Document how to deal with a stack trace that has a lot of inlining. by fergal@chromium.org
https://chromium.googlesource.com/chromium/src/+/525ee5e59c1a8549a8e99e45ff05dbd9b05a92d4
decode-lossless-webp: 1.259e+04 → 1.274e+04 (+149.8)

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

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

Regression came from new AFDO data, adding this to the list in

https://crbug.com/889742