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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg5rSKkQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg5qq5pAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghp3ErQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg5qDKpwoM


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

chromium-rel-mac11
chromium-rel-mac11-air
chromium-rel-mac12
chromium-rel-mac12-mini-8gb

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

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

Suspected Commit
  Author : nednguyen
  Commit : 0ebf7116bec925d8d6dd90b5760953ad5be6a383
  Date   : Wed May 24 09:56:02 2017
  Subject: Rerecord browse:social:twitter story & reenable the story

Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_social/browse_social_twitter
  Change       : 74.45% | 53057500.0 -> 92556680.0

Revision             Result                    N
chromium@474150      53057500 +- 1617664       6      good
chromium@474196      53321841 +- 2939964       6      good
chromium@474219      53652688 +- 2598241       6      good
chromium@474231      53005078 +- 1320094       5      good
chromium@474232      93354777 +- 9904739       6      bad       <--
chromium@474233      93137496 +- 14965474      6      bad
chromium@474234      93553465 +- 12036172      6      bad
chromium@474237      90145475 +- 4578576       6      bad
chromium@474242      92556680 +- 11598698      6      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 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.twitter system_health.memory_desktop

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

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


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