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

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


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

android-nexus5
android-nexus6
android-webview-nexus5X
android-webview-nexus6

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

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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-total_max/browse_news/browse_news_cnn

Revision             Result                  N
chromium@515092      129.666 +- 11.923       21      good
chromium@515122      169.569 +- 581.827      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.news.cnn v8.runtimestats.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: c8cd83bc1454ad04b789aa163ba4904ede582bde
  bad_revision : 1c14070930d43d2a0ed8b5b71f0e1cae8e4e07d8

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-full-mark-compactor_max/browse_social/browse_social_instagram

Revision             Result                  N
chromium@514474      45.5298 +- 8.72187      4        good
chromium@514556      43.0713 +- 2.50831      4        good
chromium@514601      42.7633 +- 4.34303      4        good
chromium@514622      42.5375 +- 5.10908      4        good
chromium@514632      44.6792 +- 5.84499      4        good
chromium@514637      43.136 +- 6.28451       4        good
chromium@514639      45.8998 +- 3.82416      5        good
chromium@514640      ---                     ---      build failure
chromium@514642      69.9519 +- 4.90721      8        bad
chromium@514816      70.6209 +- 9.00679      8        bad
chromium@515160      68.4616 +- 3.95708      10       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.instagram v8.runtimestats.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection

This regression has been open for half a year. It's not very actionable and the regression has been in all Chrome user's hands for months.