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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgyr68oAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgyo2gswsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgysmrpgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgirT_swkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg8t3AjwgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgypO_rwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgyo20qgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgiteyqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgypzwoAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgyuPAsAoM


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

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

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-memory-mark-compactor_avg/browse_tools/browse_tools_maps

Revision             Result                  N
chromium@469644      12.5981 +- 6.03444      4      good
chromium@469760      27.9557 +- 12.889       3      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.tools.maps v8.runtimestats.browsing_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8980088413590592896

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5888599767121920


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-memory-mark-compactor_avg/browse_tools/browse_tools_maps

Revision             Result                 N
chromium@469644      13.625 +- 2.42184      2      good

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.tools.maps v8.runtimestats.browsing_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8980061989350819040

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5888599767121920


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

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

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-memory-mark-compactor_avg/browse_news/browse_news_reddit
  Change       : 66.40% | 19.0011 -> 31.6186904762

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/v8/v8.git/+log/b7b3781b8747d597cf0910c65221ad2b1881e0e4..d380c7da6df1fdd995688afd2c86a573852ecd73


Revision                           Result                  N
chromium@469644                    19.0011 +- 12.6525      10       good
chromium@469652                    22.9065 +- 13.1768      12       good
chromium@469654                    22.4763 +- 12.8942      6        good
chromium@469654,v8@b7b3781b87      22.0823 +- 17.6334      10       good
chromium@469654,v8@8833af23e9      ---                     ---      build failure
chromium@469654,v8@d380c7da6d      36.3019 +- 20.083       5        bad
chromium@469654,v8@3d76d2a2dc      34.0395 +- 21.5527      8        bad
chromium@469654,v8@fbd7754947      42.3255 +- 21.7322      7        bad
chromium@469655                    37.7768 +- 14.0754      7        bad
chromium@469656                    42.0392 +- 20.7681      9        bad
chromium@469659                    38.2189 +- 15.2622      5        bad
chromium@469673                    45.0605 +- 5.37652      4        bad
chromium@469702                    34.0532 +- 25.2201      5        bad
chromium@469760                    31.6187 +- 17.4107      7        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.reddit v8.runtimestats.browsing_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979993993800619184

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5833632440123392


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

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

Suspected Commit
  Author : hpayer
  Commit : 8833af23e9788c725b0887446915e4820383a385
  Date   : Fri May 05 11:24:02 2017
  Subject: [heap] Memory reducer calls GC with kGCCallbackFlagCollectAllExternalMemory flag.

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-memory-mark-compactor_max/browse_news/browse_news_reddit
  Change       : 37.10% | 31.8397058824 -> 43.6508181818

Revision                           Result                  N
chromium@469644                    31.8397 +- 28.9784      17      good
chromium@469654                    30.725 +- 11.2883       6       good
chromium@469654,v8@516d8438ad      30.1341 +- 12.0533      8       good
chromium@469654,v8@b7b3781b87      28.7033 +- 18.7638      6       good
chromium@469654,v8@8833af23e9      51.5981 +- 49.6077      10      bad       <--
chromium@469655                    57.0971 +- 47.3238      10      bad
chromium@469656                    44.9227 +- 34.0006      7       bad
chromium@469657                    54.2964 +- 39.7708      5       bad
chromium@469659                    57.8246 +- 46.5709      9       bad
chromium@469673                    50.574 +- 24.4279       5       bad
chromium@469701                    63.4713 +- 26.867       4       bad
chromium@469760                    43.6508 +- 40.6427      11      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.reddit v8.runtimestats.browsing_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979993984663497648

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6269486862172160


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!