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

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


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

android-webview-nexus6

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

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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:gpu:effective_size_avg/foreground/https_mobile_twitter_com_justinbieber_skip_interstitial_true

Revision             Result                   N
chromium@524132      2755048 +- 37004351      21      good
chromium@524201      6684867 +- 53691555      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=https.mobile.twitter.com.justinbieber.skip.interstitial.true 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/8960120259784365936


For feedback, file a bug with component Speed>Bisection

I cannot say from the graph if this is a regression for sure. I will wait a few days for more data points and triage if it looks like a regression.

Juan: There was a jump in noise here, which went away, then maybe came back in  bug 804862 . I'm WontFix-ing since it went away, but feel free to file another bug on the noise if you think it would help.