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

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


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

android-nexus5X

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

=== 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_nexus5X_perf_bisect
  Benchmark    : thread_times.key_mobile_sites_smooth
  Metric       : thread_other_cpu_time_per_frame/http___www.reddit.com_r_programming_comments_1g96ve

Revision             Result                    N
chromium@506691      0.335187 +- 0.585697      21      good
chromium@506711      0.261026 +- 0.462668      21      unknown
chromium@506731      0.239715 +- 0.383865      21      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=http...www.reddit.com.r.programming.comments.1g96ve 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/8965831513526981376


For feedback, file a bug with component Speed>Bisection

Bisect unable to find culprit, this regression exists in stable. Ignoring.