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

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


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

android-webview-nexus5X

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

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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/background/after_http_m_youtube_com_results_q_science

Revision             Result                   N
chromium@507816      38416542 +- 754688       21      good
chromium@507863      38381190 +- 1104451      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=http.m.youtube.com.results.q.science memory.top_10_mobile

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

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


For feedback, file a bug with component Speed>Bisection

Bisect could not find a culprit. The graph is noisy and it looks like it is now back down to pre-this-regression levels.