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

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


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

android-nexus5
android-webview-nexus6

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8972445469687354864

=== Auto-CCing suspected CL author mtklein@chromium.org ===

Hi mtklein@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Mike Klein
  Commit : 5f9b59b52db2b9a11d41bb7fa93ec5e5d6104236
  Date   : Sat Jul 29 12:28:32 2017
  Subject: use new Stage ABI for ARMv7 too

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : thread_times.key_mobile_sites_smooth
  Metric       : thread_other_cpu_time_per_frame/http___cuteoverload.com
  Change       : 46.99% | 2.02102234499 -> 2.97074527227

Revision                             Result                   N
chromium@490643                      2.02102 +- 0.539188      6      good
chromium@490655                      1.70516 +- 1.50347       6      good
chromium@490658                      1.71845 +- 0.70621       6      good
chromium@490660                      1.78335 +- 0.558717      6      good
chromium@490660,skia@5f9b59b52d      3.28538 +- 1.03334       6      bad       <--
chromium@490661                      2.91095 +- 0.332054      6      bad
chromium@490667                      2.97075 +- 0.522368      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...cuteoverload.com thread_times.key_mobile_sites_smooth

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8972445469687354864


For feedback, file a bug with component Speed>Bisection

This is not the same CL but part of the same ongoing effort mentioned at 747873.  Like in that bug, this is limited to cuteoverload, and it even looks like the CL in question here actually fixed many of the regressions there in 747873.  The regressions here are still to levels better than where we were less than a month ago.