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

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


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

perf-go-webview-phone

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

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

Bisect Details
  Configuration: go-webview-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:cc:effective_size_avg/background_tools/background_tools_gmail
  Change       : 0.00% | 3969024.0 -> 3969024.0

Revision                       Result              N
android-chrome@8257df3404      3969024 +- 0.0      21      good
android-chrome@ab26e7ad9f      3969024 +- 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=background.tools.gmail 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/8945185589371424976


For feedback, file a bug with component Speed>Bisection