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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg5qvNsgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglqbCtgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglrDAugsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg5sX6qAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglsjftAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg5pv19AkM


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

chromium-rel-mac-retina
chromium-rel-mac11-pro
chromium-rel-win10

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

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

Suspected Commit
  Author : mek
  Commit : c8e2b27f71c6792fa1072fa98a22c111ad229090
  Date   : Tue Jun 06 23:18:28 2017
  Subject: Switch to mojo localstorage backend by default.

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_news/load_news_wikipedia
  Change       : 9.69% | 16985719.0 -> 18636358.1111

Revision             Result                   N
chromium@477389      16985719 +- 1618586      9      good
chromium@477447      16949903 +- 2000310      9      good
chromium@477455      16929968 +- 1147705      6      good
chromium@477457      16931770 +- 1165670      6      good
chromium@477458      18566219 +- 1165278      6      bad       <--
chromium@477459      18572108 +- 1203621      6      bad
chromium@477462      18487302 +- 1183173      9      bad
chromium@477476      18471731 +- 1290497      9      bad
chromium@477505      18636358 +- 1632424      9      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=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.news.wikipedia system_health.memory_desktop

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

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


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