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

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


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

chromium-rel-win10

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

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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_games/load_games_alphabetty

Revision             Result                   N
chromium@490656      15122822 +- 2721877      21      good
chromium@490669      15047924 +- 2084632      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.games.alphabetty 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/8972207406284164368


For feedback, file a bug with component Speed>Bisection

This is probably just noise :(