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

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


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

android-nexus5
android-nexus6
android-nexus7v2
android-webview-nexus6

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

=== BISECT JOB RESULTS ===
Bisect failed unexpectedly

Bisect was aborted with the following:
  Step('Check bisect finished on revision chromium@514641.fetch file 2f5601bcf02b54c5b68b10520223a993469abd42:DEPS') failed with return_code 1


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-total_max/browse_social/browse_social_facebook_infinite_scroll

Revision             Result                  N
chromium@514611      38.2476 +- 59.1012      14      good
chromium@514636      41.8055 +- 55.0385      14      good
chromium@514640      41.9802 +- 55.7685      9       good
chromium@514641      49.6377 +- 31.363       9       good
chromium@514642      76.6034 +- 65.4757      9       bad
chromium@514643      84.3955 +- 11.2623      6       bad
chromium@514649      67.9041 +- 127.057      21      bad
chromium@514661      69.5142 +- 100.726      14      bad
chromium@514710      68.813 +- 100.382       14      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.facebook.infinite.scroll 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/8962312073167163680


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : Ulan Degenbaev
  Commit : 6bb1d47e6e82f75ead36cdab209afc5dafa8329c
  Date   : Tue Nov 07 13:11:10 2017
  Subject: [heap] Re-enable concurrent marking.

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-total_max/browse_social/browse_social_instagram
  Change       : 55.61% | 71.4211666667 -> 111.139666667

Revision                           Result                  N
chromium@514533                    71.4212 +- 9.60797      6      good
chromium@514588                    65.3942 +- 37.0616      6      good
chromium@514616                    73.2525 +- 7.9254       6      good
chromium@514630                    74.112 +- 6.46166       6      good
chromium@514637                    70.2515 +- 7.24476      6      good
chromium@514640                    71.6755 +- 8.48655      6      good
chromium@514641                    74.3308 +- 4.99465      6      good
chromium@514641,v8@67d543ec31      74.4882 +- 13.1025      6      good
chromium@514641,v8@6bb1d47e6e      114.329 +- 5.17608      6      bad       <--
chromium@514641,v8@ac0661b358      113.663 +- 3.77887      6      bad
chromium@514641,v8@80cb266c75      112.386 +- 8.58561      6      bad
chromium@514642                    114.172 +- 6.98079      6      bad
chromium@514643                    111.14 +- 6.76137       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.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/8962235628159361200


For feedback, file a bug with component Speed>Bisection