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

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


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

android-nexus6

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : thread_times.simple_mobile_sites
  Metric       : thread_IO_cpu_time_per_frame/thread_IO_cpu_time_per_frame


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 thread_times.simple_mobile_sites

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

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


For feedback, file a bug with component Speed>Bisection

Duping to https://bugs.chromium.org/p/chromium/issues/detail?id=744674 - an almost identical benchmark ended up there in the same range.