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

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


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

android-webview-nexus5X

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

=== Auto-CCing suspected CL author perezju@chromium.org ===

Hi perezju@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Juan A. Navarro Perez
  Commit : 59bf3021bcf91a57dd3e3972c9cfcb0c8e83b117
  Date   : Tue Sep 12 14:58:15 2017
  Subject: [tools/perf] Tweak memory.top_10_mobile story flow

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:cc:effective_size_avg/background/after_http_m_youtube_com_results_q_science
  Change       : 232.55% | 7798784.0 -> 25934506.6667

Revision             Result                    N
chromium@501243      7798784 +- 0.0            6      good
chromium@501267      7798784 +- 0.0            6      good
chromium@501273      7798784 +- 0.0            6      good
chromium@501274      25625259 +- 11875036      6      bad       <--
chromium@501275      21359275 +- 15838151      6      bad
chromium@501276      23558144 +- 15119748      6      bad
chromium@501279      19113984 +- 14951668      6      bad
chromium@501291      25934507 +- 12265447      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=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests 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/8968559634961631840


For feedback, file a bug with component Speed>Bisection

 Issue 764717  has been merged into this issue.

Issue 765126 has been merged into this issue.

These are expected and make sense as we made some changes to the benchmark logic.

The larger regressions are on background, which also makes sense, since before we were loading about:blank before going to background, and we don't anymore.

Issue 766602 has been merged into this issue.