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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=f90c7b78bf863f44804aee4d3e5ff46720886c300af0b3dfc34b62f5ca8258f8


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

chromium-rel-mac12

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

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

Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/browse_media/browse_media_tumblr

Revision             Result                   N
chromium@511904      63771060 +- 5738156      21      good
chromium@512046      63668230 +- 4788918      21      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.tumblr system_health.memory_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8964184550555152496


For feedback, file a bug with component Speed>Bisection

Bisect can't repro, and the ref build jumped too. Must be a change on the machine.