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

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


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

android-nexus5
android-nexus5X
android-nexus6

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

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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-incremental-step_max/browse_social/browse_social_facebook

Revision             Result                  N
chromium@515451      4.21557 +- 7.50552      21      good
chromium@515515      4.99467 +- 14.1648      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.facebook 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/8962312542027534608


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : Michael Lippautz
  Commit : 667555c6b8dadcfe4e592fe06bb6846468b8141e
  Date   : Thu Nov 09 17:29:11 2017
  Subject: [heap] Remove independent handles

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-latency-mark-compactor_sum/browse_social/browse_social_instagram
  Change       : 114.34% | 7.324 -> 16.4970714286

Revision                           Result                  N
chromium@515346                    7.324 +- 2.53868        6       good
chromium@515431                    7.09888 +- 1.35056      8       good
chromium@515453                    6.883 +- 2.42662        5       good
chromium@515456                    7.55313 +- 3.42728      8       good
chromium@515457                    7.141 +- 2.14271        5       good
chromium@515457,v8@667555c6b8      16.8785 +- 3.46184      6       bad       <--
chromium@515457,v8@62a720354c      17.4345 +- 5.63066      6       bad
chromium@515457,v8@02c84d4192      16.484 +- 1.62094       6       bad
chromium@515458                    15.523 +- 5.6828        6       bad
chromium@515459                    15.7512 +- 8.86064      9       bad
chromium@515464                    16.2266 +- 10.3395      9       bad
chromium@515474                    15.3361 +- 8.10203      9       bad
chromium@515516                    16.4971 +- 11.5909      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.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/8962234138754186384


For feedback, file a bug with component Speed>Bisection