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

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


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

chromium-rel-mac11
chromium-rel-mac11-air
chromium-rel-mac11-pro

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

=== 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/load_media/load_media_dailymotion

Revision             Result                    N
chromium@500300      26410285 +- 23195008      21      good
chromium@500363      28850635 +- 936118        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=load.media.dailymotion 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/8968743699224005776


For feedback, file a bug with component Speed>Bisection

Same regression on ref.