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

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


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

android-webview-nexus5X

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

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

Hi mlippautz@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 : Michael Lippautz
  Commit : 4d95c4b0c97eb689254a2a74c0cf1dd1acaba7f9
  Date   : Tue Dec 05 16:56:35 2017
  Subject: [heap] Lower limit for maximum number of unmapper tasks

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_games/load_games_bubbles
  Change       : 2.42% | 40853954.6667 -> 41843138.6667

Revision                           Result                   N
chromium@521893                    40853955 +- 1849216      9       good
chromium@521924                    40740973 +- 1730442      9       good
chromium@521928                    40657005 +- 1596290      9       good
chromium@521928,v8@7ffc331d64      40809809 +- 1422303      9       good
chromium@521928,v8@c91e707bee      40943091 +- 1104785      14      good
chromium@521928,v8@355e2f0888      40925976 +- 1373161      6       good
chromium@521928,v8@4d95c4b0c9      42129517 +- 570767       6       bad       <--
chromium@521928,v8@b4470ea4cf      42286531 +- 1623676      6       bad
chromium@521929                    41619224 +- 1125244      9       bad
chromium@521930                    42016877 +- 1865967      9       bad
chromium@521932                    41964084 +- 1661011      9       bad
chromium@521940                    41717414 +- 2123375      9       bad
chromium@521955                    41843139 +- 795007       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 --story-filter=load.games.bubbles 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/8960740518232963872


For feedback, file a bug with component Speed>Bisection

Timing change. Nothing to do here.