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

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


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

android-webview-nexus5X

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

=== 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:cc:effective_size_avg/browse_media/browse_media_imgur

Revision             Result                     N
chromium@505782      155928784 +- 27818687      21      good
chromium@506403      160690904 +- 0.0           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=browse.media.imgur 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/8966019686557782144


For feedback, file a bug with component Speed>Bisection

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