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

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


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

chromium-rel-mac11

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg

Suspected Commit Range
  159 commits in range
  https://chromium.googlesource.com/chromium/src/+log/949b36db0565e9a81fc50cbb1584d64d6090c147..877fb8bd29acf269d27688444a50c36f9332e946


Revision             Result                  N
chromium@445283      35960297 +- 604725      9      good
chromium@445442      36477790 +- 616561      6      bad
chromium@445600      36584262 +- 557593      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 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests system_health.memory_desktop

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

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


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

Hit 24 hour timeout: crbug.com/676350

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

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

Suspected Commit
  Author : mvstanton
  Commit : 55feaaea4c83bf72a409bb1ebde5b86c979d4d1c
  Date   : Thu Jan 19 17:12:28 2017
  Subject: Revert [TypeFeedbackVector] Root literal arrays in function literal slots

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:heap:effective_size_avg/browse_media/browse_media_imgur
  Change       : 19.40% | 93241434.6667 -> 111333641.778

Revision                           Result                     N
chromium@445200                    93241435 +- 7370236        9       good
chromium@445275                    93693477 +- 7411963        9       good
chromium@445280                    94191072 +- 3972061        6       good
chromium@445283                    98441869 +- 18032154       9       good
chromium@445283,v8@f09e57923a      98748548 +- 23643093       14      good
chromium@445283,v8@7ff8d317b1      97444927 +- 15623174       9       good
chromium@445283,v8@f604724448      92322011 +- 11782597       6       good
chromium@445283,v8@55feaaea4c      112092850 +- 34373306      14      bad       <--
chromium@445283,v8@5e44cc79d5      113310838 +- 27115162      9       bad
chromium@445283,v8@c70ec473ba      112780633 +- 39262194      14      bad
chromium@445283,v8@e26a58e43c      116781301 +- 33281564      14      bad
chromium@445284                    119361839 +- 20929292      9       bad
chromium@445285                    117017605 +- 14279258      6       bad
chromium@445294                    111992336 +- 25175400      6       bad
chromium@445313                    112269612 +- 21370099      6       bad
chromium@445350                    111333642 +- 35230594      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 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.imgur system_health.memory_desktop

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

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


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

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

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg

Revision             Result                  N
chromium@445283      34827990 +- 362070      6      good
chromium@445600      34900157 +- 464885      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 system_health.memory_desktop

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

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


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