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

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


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

android-nexus5X

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@427364  3320690  100.781  5  good
chromium@427390  3334379  230.866  5  bad
chromium@427416  3336837  5165.78  5  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 661508

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests system_health.memory_mobile
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/blank_about/blank_about_blank
Relative Change: 0.49%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/822
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997110532615369392


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

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