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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgiof7tQoM


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

android-nexus5

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

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : blink_perf.paint
  Metric       : complex-content-slow-scroll/complex-content-slow-scroll


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 blink_perf.paint

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

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


| 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/8980148805064951408

=== 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_nexus5_perf_bisect
  Benchmark    : blink_perf.paint
  Metric       : complex-content-slow-scroll/complex-content-slow-scroll
  Change       : 105.14% | 38.54 -> 79.0610833333

Revision                           Result                   N
chromium@469631                    38.54 +- 1.97217         6      good
chromium@469647                    37.8966 +- 1.57028       6      good
chromium@469651                    37.3701 +- 0.658717      6      good
chromium@469653                    37.5414 +- 0.852487      6      good
chromium@469654                    38.1023 +- 0.954643      6      good
chromium@469654,v8@25959abf79      38.0289 +- 2.58026       6      good
chromium@469654,v8@b7b3781b87      37.1929 +- 1.07566       6      good
chromium@469654,v8@8833af23e9      78.3097 +- 3.87486       6      bad       <--
chromium@469655                    79.5725 +- 2.82045       6      bad
chromium@469662                    79.0611 +- 5.0895        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 blink_perf.paint

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

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


| 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_nexus5_perf_bisect
  Benchmark    : blink_perf.paint
  Metric       : complex-content-slow-scroll/complex-content-slow-scroll
  Change       : 110.05% | 37.646 -> 79.07575

Revision                           Result                   N
chromium@469631                    37.646 +- 2.93129        6      good
chromium@469647                    38.2301 +- 1.32578       6      good
chromium@469651                    37.0723 +- 0.993555      6      good
chromium@469653                    37.9992 +- 1.92248       6      good
chromium@469654                    37.7063 +- 1.69406       6      good
chromium@469654,v8@25959abf79      38.4125 +- 1.51297       6      good
chromium@469654,v8@b7b3781b87      38.3455 +- 2.50647       6      good
chromium@469654,v8@8833af23e9      78.75 +- 3.46853         6      bad       <--
chromium@469655                    79.4654 +- 2.63919       6      bad
chromium@469662                    79.0758 +- 2.03064       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 blink_perf.paint

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

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


| 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!