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

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


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

android-nexus5X
android-nexus6
android-nexus7v2
chromium-rel-mac-retina
chromium-rel-mac11
chromium-rel-mac11-air
chromium-rel-mac12
chromium-rel-win10
chromium-rel-win7-gpu-intel
chromium-rel-win8-dual

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : speedometer
  Metric       : VanillaJS-TodoMVC/VanillaJS-TodoMVC
  Change       : 1.64% | 168.986619048 -> 171.755535714

Suspected Commit Range
  3 commits in range
  https://chromium.googlesource.com/chromium/src/+log/dacc670f59624580b516fb299150c4ea8a7b7f72..251266ac46bf8c9fd0dc3b1fe4a23b881c818a5a


Revision             Result                  N
chromium@496636      168.987 +- 7.38924      21       good
chromium@496653      168.832 +- 9.56337      21       good
chromium@496657      168.562 +- 5.68915      9        good
chromium@496659      168.831 +- 5.26791      14       good
chromium@496660      ---                     ---      build failure
chromium@496661      ---                     ---      build failure
chromium@496662      172.865 +- 15.5557      14       bad
chromium@496668      171.756 +- 13.4594      14       bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests speedometer

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

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


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : Brian White
  Commit : 7662ff8cb53121cd4d8916007d430b36efd45895
  Date   : Thu Aug 24 00:03:13 2017
  Subject: Validate histograms before and after each task on Android.

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : speedometer2
  Metric       : Total/Speedometer2
  Change       : 1.67% | 81102.9769444 -> 82454.0877778

Revision             Result                  N
chromium@496667      81103.0 +- 733.593      6      good
chromium@496809      81777.2 +- 517.131      6      good
chromium@496845      81328.5 +- 984.26       6      good
chromium@496863      81669.8 +- 951.559      6      good
chromium@496872      81231.7 +- 472.041      6      good
chromium@496876      81069.9 +- 561.078      6      good
chromium@496877      81443.6 +- 1267.77      6      good
chromium@496878      82983.3 +- 1237.13      6      bad       <--
chromium@496880      83220.0 +- 959.752      6      bad
chromium@496950      82454.1 +- 536.873      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=Speedometer2 speedometer2

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

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


For feedback, file a bug with component Speed>Bisection