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

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


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

android-nexus5

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : total:500ms_window:renderer_eqt_max/browse_social/browse_social_tumblr_infinite_scroll

Revision             Result                  N
chromium@512835      2021.23 +- 1182.92      21      good
chromium@512929      2092.03 +- 921.089      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=browse.social.tumblr.infinite.scroll v8.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : Koji Ishii
  Commit : 811fe6a25ddee5065812bf50733de963e58832cb
  Date   : Tue Oct 31 14:34:37 2017
  Subject: Add CrashKey to LazyLineBreakIterator on Android

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : total:500ms_window:renderer_eqt_max/browse_social/browse_social_tumblr_infinite_scroll
  Change       : 109.81% | 985.762833333 -> 2068.22983333

Revision             Result                  N
chromium@512439      985.763 +- 121.566      6      good
chromium@512720      1047.04 +- 106.631      6      good
chromium@512790      967.912 +- 108.045      6      good
chromium@512808      1092.47 +- 465.64       6      good
chromium@512817      1021.88 +- 178.298      6      good
chromium@512821      797.866 +- 886.7        6      good
chromium@512823      1008.6 +- 171.238       6      good
chromium@512824      978.22 +- 147.507       6      good
chromium@512825      2054.86 +- 552.823      6      bad       <--
chromium@512860      1996.22 +- 505.219      6      bad
chromium@513000      2068.23 +- 215.788      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=browse.social.tumblr.infinite.scroll v8.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection