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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg86aytwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg85LW6QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg89qdvwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg89X8qQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgi9zJpgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg88eFpgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgi9KwtgoM


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

android-nexus5
android-nexus9

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@430919  4647999  3416333  27  good
chromium@430924  4611947  3345454  27  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 665339

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_http_m_youtube_com_results_q_science
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4342
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995942202670374912


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

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N   Good?
chromium@430919  74303196  4005521  27  good
chromium@430989  74690192  4751415  27  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 665339

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=https.www.google.co.uk.hl.en.q.science memory.top_10_mobile
Test Metric: memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/background/after_https_www_google_co_uk_hl_en_q_science
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2267
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995862082484057744


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

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

These regressions happened before M56 branch. M56 is now in stable. These regressions made it to the stable channel. Marking wontfix.

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

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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_http_m_youtube_com_results_q_science

Revision             Result                  N
chromium@430919      4647999 +- 3416333      27      good
chromium@430924      4611947 +- 3345454      27      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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 memory.top_10_mobile

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

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


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