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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgotiSsQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgoqL-pgsM


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

chromium-rel-win7-dual

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N   Good?
chromium@401926  26582282  5195273  12  good
chromium@401972  26014243  4838957  18  bad

Bisect job ran on: win_perf_bisect
Bug ID: 623665

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests v8.infinite_scroll
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_max/tumblr
Relative Change: 14.17%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6621
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9008675308448728928


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5863530360733696

| 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 Tests>AutoBisect.  Thank you!

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Lan, can you follow up on this?

From the instructions (https://chromium.googlesource.com/chromium/src/+/master/tools/perf/docs/perf_regression_sheriffing.md):
"After your shift, please try to follow up on the bugs you filed weekly. Kick off new bisects if the previous ones failed, and if the bisect picks a likely culprit follow up to ensure the CL author addresses the problem. If you are certain that a specific CL caused a performance regression, and the author does not have an immediate plan to address the problem, please revert the CL."

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

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

Trying some more bisects.

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N   Good?
chromium@401926  25538819  4944002  12  good
chromium@401972  28010646  4420978  18  bad

Bisect job ran on: win_perf_bisect
Bug ID: 623665

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests v8.infinite_scroll
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_max/tumblr
Relative Change: 12.26%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6727
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006405764076518304


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5781370303938560

| 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 Tests>AutoBisect.  Thank you!

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N   Good?
chromium@401926  17875098  2442032  12  good
chromium@401972  18647453  2428634  18  bad

Bisect job ran on: win_perf_bisect
Bug ID: 623665

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests v8.infinite_scroll
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_avg/tumblr
Relative Change: 14.00%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6726
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006405783175205792


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5230391632330752

| 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 Tests>AutoBisect.  Thank you!

Friendly perf-sheriff ping, could your patch have caused this regression?

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

There's no patch implicated yet.

Sending off a wider bisect.

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N   Good?
chromium@401868  27652033  3446770  18  good
chromium@401972  27061309  4884115  12  bad

Bisect job ran on: win_perf_bisect
Bug ID: 623665

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests v8.infinite_scroll
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_max/tumblr
Relative Change: 15.16%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6806
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005128776228276256


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5846330736377856

| 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 Tests>AutoBisect.  Thank you!

Perf sheriff ping: reminder to follow up on possible performance issues

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

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

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N   Good?
chromium@401926  18239505  2376289  12  good
chromium@401972  19466779  2421596  18  bad

Bisect job ran on: win_perf_bisect
Bug ID: 623665

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests v8.infinite_scroll
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_avg/tumblr
Relative Change: 2.08%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6858
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9003875540996641120


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5291559390543872

| 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 Tests>AutoBisect.  Thank you!

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N   Good?
chromium@401926  26810571  4787262  12  good
chromium@401972  27552387  5282724  18  bad

Bisect job ran on: win_perf_bisect
Bug ID: 623665

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests v8.infinite_scroll
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_max/tumblr
Relative Change: 6.82%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6857
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9003875553076721456


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5551323039137792

| 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 Tests>AutoBisect.  Thank you!

perf sheriff fixit: unsetting perf sheriffs as bug owners to clarify the rotation triages the bugs.

This is old, and the graphs aren't loading.
Marking WontFix.