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

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


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

android-one

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

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

Hi bcwhite@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 : Brian White
  Commit : 003796b6cd67a5ec5d1dd12577f811719cf4122d
  Date   : Sat Sep 02 18:31:07 2017
  Subject: Do histogram validation after every JNI call.

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_total_all_cpu_time_per_frame/infinite_scrolling.html
  Change       : 49.07% | 27.6169506434 -> 41.1682110327

Revision             Result                   N
chromium@499395      27.617 +- 0.169999       6      good
chromium@499399      27.3994 +- 0.821645      6      good
chromium@499400      41.0654 +- 2.11388       6      bad       <--
chromium@499401      41.1844 +- 0.960196      6      bad
chromium@499402      41.1682 +- 3.78931       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=infinite.scrolling.html thread_times.key_silk_cases

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

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


For feedback, file a bug with component Speed>Bisection