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

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


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

Android Nexus6 WebView Perf

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/17d677b6e40000

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

Roll AFDO from 71.0.3576.0_rc-r1 to 71.0.3577.0_rc-r1 by chromium-autoroll@skia-public.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/6fb1a0860e442c7f9707c2003d219cb03b3dff81
insert-before: 43.28 → 35.09 (-8.196)

Rename WebThread to Thread in the entire code base. by yutak@chromium.org
https://chromium.googlesource.com/chromium/src/+/625d998496348a053dd112fc5b6c09364633882e
insert-before: 34.42 → 35.5 (+1.085)

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

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

This seems like a false alert according to the graph.