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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkvHp-ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg4pfd5wkM


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

android-nexus5X

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.infinite_scroll-classic_tbmv2
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_max/flickr

Revision             Result                   N
chromium@465554      32999928 +- 2479761      2       good
chromium@465689      52513901 +- 4918469      19      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=flickr v8.infinite_scroll-classic_tbmv2

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

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


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

=== Auto-CCing suspected CL author msramek@chromium.org ===

Hi msramek@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : msramek
  Commit : dbeec5901f1471800a86dabd60afbde6544bc69c
  Date   : Wed Apr 19 15:45:20 2017
  Subject: Disable the flaky test CopylessPasteTest#testCache

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.infinite_scroll-classic_tbmv2
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_max/flickr
  Change       : 65.26% | 32140088.0 -> 53115329.6

Revision             Result                   N
chromium@465554      32140088 +- 1383507      3       good
chromium@465588      36433027 +- 7245636      3       good
chromium@465606      34147352 +- 1466765      3       good
chromium@465614      32106232 +- 1787006      3       good
chromium@465617      33157835 +- 3463466      3       good
chromium@465620      51930006 +- 2939808      8       good
chromium@465621      53499116 +- 3375286      19      bad       <--
chromium@465622      52828103 +- 4240760      18      bad
chromium@465689      53115330 +- 4262421      20      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=flickr v8.infinite_scroll-classic_tbmv2

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

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


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

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

Suspected Commit
  Author : hablich
  Commit : 990315f377a2df9604edcad7b6f9c2d1c53dd059
  Date   : Wed Apr 19 15:41:18 2017
  Subject: Revert of [scheduler] Move some task types to suspendable task runner. (patchset #1 id:1 of https://codereview.chromium.org/2808273003/ )

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.infinite_scroll-classic_tbmv2
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/flickr
  Change       : 30.88% | 30837226.6667 -> 40360858.8889

Revision             Result                   N
chromium@465554      30837227 +- 2977742      3       good
chromium@465587      31523824 +- 3764221      4       good
chromium@465606      30730343 +- 1782077      3       good
chromium@465614      33402877 +- 4300942      3       good
chromium@465618      30232745 +- 2205183      3       good
chromium@465619      40659650 +- 5418707      20      bad       <--
chromium@465620      40649746 +- 4754502      18      bad
chromium@465622      40270331 +- 5037718      19      bad
chromium@465689      40360859 +- 4579525      18      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=flickr v8.infinite_scroll-classic_tbmv2

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

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


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