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

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


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

chromium-rel-mac12

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

=== 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:gpu:effective_size_avg/load_news/load_news_qq

Revision             Result                   N
chromium@502784      18913250 +- 7203842      21      good
chromium@502817      19340760 +- 8726830      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.news.qq 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/8967712630439794768


For feedback, file a bug with component Speed>Bisection

One metric has recovered and the regression in the other one coincides with changes in the reference metric. Closing.