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

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


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

chromium-rel-mac11
chromium-rel-mac12-mini-8gb
chromium-rel-win7-dual

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

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

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

Revision             Result                   N
chromium@511764      61153280 +- 7248175      21      good
chromium@511812      61047174 +- 9572411      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.tools.gmail 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/8963949042571778016


For feedback, file a bug with component Speed>Bisection