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

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


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

android-nexus5
android-nexus5X
android-webview-nexus5X
android-webview-nexus6
chromium-rel-mac12
chromium-rel-win10

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

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

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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:gpu:effective_size_avg/load_games/load_games_spychase

Revision             Result                  N
chromium@507628      6556194 +- 2153.25      21      good
chromium@507657      6556559 +- 3185.98      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=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.games.spychase system_health.memory_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8965933664176490400


For feedback, file a bug with component Speed>Bisection

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: df007e1a7ae808ad41eb2bd01f6a658c5b438285
  bad_revision : 29380bdd56526168d8f8e54d641a1f16b205da4d

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/load_search/load_search_taobao

Revision                             Result              N
chromium@507629                      2146384 +- 0.0      6      good
chromium@507652                      2146384 +- 0.0      6      good
chromium@507658                      2146384 +- 0.0      6      good
chromium@507661                      2146384 +- 0.0      6      good
chromium@507662                      2146384 +- 0.0      6      good
chromium@507662,skia@df007e1a7a      2146384 +- 0.0      6      good
chromium@507662,skia@29380bdd56      4243536 +- 0.0      6      bad
chromium@507662,skia@3f98552933      4243536 +- 0.0      6      bad
chromium@507663                      4243536 +- 0.0      6      bad
chromium@507674                      4243536 +- 0.0      6      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/8965933836610608224


For feedback, file a bug with component Speed>Bisection

Bisect unable to find culprit, this regression exists in stable. Ignoring.