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

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


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

chromium-rel-win7-gpu-ati

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: winx64ati_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_search/load_search_taobao
  Change       : 5.82% | 209677012.048 -> 197468579.857

Suspected Commit Range
  6 commits in range
  https://chromium.googlesource.com/chromium/src/+log/06e980861f8b1a81c4d5da2f667f44336cab385d..f9cc972addbcd3f856a0bfc595d1bf62c0824f82


Revision             Result                     N
chromium@480312      209677012 +- 6432228       21       good
chromium@480332      209952112 +- 6139560       14       good
chromium@480341      209660708 +- 4435057       14       good
chromium@480342      ---                        ---      build failure
chromium@480343      ---                        ---      build failure
chromium@480344      ---                        ---      build failure
chromium@480345      ---                        ---      build failure
chromium@480346      ---                        ---      build failure
chromium@480347      200836645 +- 41978377      14       bad
chromium@480352      197468580 +- 44478573      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.search.taobao 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/8974476234773836000


For feedback, file a bug with component Speed>Bisection

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

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

Bisect Details
  Configuration: winx64ati_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_search/load_search_taobao

Revision             Result                     N
chromium@480312      209370858 +- 7549679       21      good
chromium@480352      201631022 +- 53286469      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.search.taobao 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/8974279017406413488


For feedback, file a bug with component Speed>Bisection