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

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


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

chromium-rel-win10

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

=== BISECT JOB RESULTS ===
Bisect failed unexpectedly

Bisect was aborted with the following:
  Step('Check bisect finished on revision chromium@492230,catapult@33a9271eb3.fetch file 33a9271eb3cf5caf925293ec6a4b47c94f1ac968:DEPS') failed with return_code 1


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_news/load_news_wikipedia

Revision                                 Result                   N
chromium@492191                          12734464 +- 642119       6       good
chromium@492211                          12622117 +- 886208       14      good
chromium@492220                          12821845 +- 605396       6       good
chromium@492227                          12647083 +- 741455       9       good
chromium@492229                          12509769 +- 2025718      14      good
chromium@492230                          12597150 +- 2084632      21      good
chromium@492230,catapult@46e88f15e5      12821845 +- 957215       6       good
chromium@492230,catapult@33a9271eb3      12705337 +- 1077309      9       good
chromium@492231                          12135278 +- 1197202      14      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.wikipedia 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/8971643959500442448


For feedback, file a bug with component Speed>Bisection

The bisect diddn't reproduce (it found an improvement) and all these graphs went back down.