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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtoOWuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1r-DuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1t_rtQkM


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

android-galaxy-s5
chromium-rel-win10
chromium-rel-win7-x64-dual

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

===== 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@410308  2078859  23494.3  12  good
chromium@410310  2073994  32231.1  12  bad

Bisect job ran on: android_s5_perf_bisect
Bug ID: 636355

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests top_10_mobile_memory
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_avg/http___m.intl.taobao.com_group-purchase.html
Relative Change: 0.23%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/908
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004710046276633024


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

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

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

Kicked off bisect on the Windows 10 bot

===== 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@410306  8790510  353187   18  good
chromium@410336  9051680  446108   18  bad

Bisect job ran on: winx64_10_perf_bisect
Bug ID: 636355

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests top_10_mobile_memory
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/http___m.intl.taobao.com_group-purchase.html
Relative Change: 2.00%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_10_perf_bisect/builds/653
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004688908429215680


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

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

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

Re-kicked bisect on the Windows bot with a wider range

===== 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@410308  8826874  205372   18  good
chromium@410332  9047193  371683   18  bad

Bisect job ran on: win_x64_perf_bisect
Bug ID: 636355

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests top_10_mobile_memory
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/http___m.intl.taobao.com_group-purchase.html
Relative Change: 3.65%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_x64_perf_bisect/builds/1400
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004255018261697312


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

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

Looks like the v8 roll:
https://chromium.googlesource.com/v8/v8/+log/fbcbbfc7..743b9df1

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

Trying another bisect to see if we can get into the v8 roll.  3 of the tests are no longer running so it's only the first graph anymore which is unfortunately also pretty noisy.

https://chromeperf.appspot.com/buildbucket_job_status/8999816601314906512

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/1056
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

perf sheriff fixit: unsetting owners of bugs owned by sheriffs to clarify the sheriffing rotation triages the bugs.

Closing as we do not have S5s to verify this regression.

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