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

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


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

chromium-rel-mac-retina
chromium-rel-mac11-pro
chromium-rel-win10

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

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

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

Revision             Result                   N
chromium@516021      21918086 +- 2282453      21      good
chromium@516124      22017950 +- 1465150      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_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.news.flipboard 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/8962313233609814928


For feedback, file a bug with component Speed>Bisection

Recovered.