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

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


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

android-nexus6

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

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

Suspected Commit
  Author : Brian White
  Commit : 1278570bd438b22d1a703d67d441d813839d44ac
  Date   : Tue Sep 05 01:25:16 2017
  Subject: Revert "Do histogram validation after every JNI call."

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : thread_times.key_idle_power_cases
  Metric       : tasks_per_second_total_all/animated-gif.html
  Change       : 4.38% | 706.72153942 -> 737.672634663

Revision             Result                  N
chromium@499528      706.722 +- 15.4163      6      good
chromium@499533      708.007 +- 18.9088      6      good
chromium@499536      709.32 +- 25.6542       6      good
chromium@499537      731.463 +- 9.82638      6      bad       <--
chromium@499538      737.673 +- 14.7915      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=animated.gif.html thread_times.key_idle_power_cases

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

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


For feedback, file a bug with component Speed>Bisection