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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzsGe-QsM


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

android-webview-nexus6

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

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

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

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

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

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

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

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

Hi mek@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 : Marijn Kruisselbrink
  Commit : 5f2725f68003a78440a8c381b258bc338e910232
  Date   : Thu Jun 22 23:51:15 2017
  Subject: Change when leveldb wrappers are purged.

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/background/after_http_yandex_ru_touchsearch_text_science
  Change       : 5.63% | 24980106.6667 -> 26386570.6667

Revision             Result                  N
chromium@481633      24980107 +- 402809      6      good
chromium@481705      24816608 +- 516784      6      good
chromium@481723      24678539 +- 420613      6      good
chromium@481724      24771723 +- 929109      6      good
chromium@481725      26453643 +- 817755      6      bad       <--
chromium@481726      26629771 +- 521439      6      bad
chromium@481728      26549387 +- 719319      6      bad
chromium@481732      26696501 +- 776655      6      bad
chromium@481741      26564235 +- 765888      6      bad
chromium@481777      26386571 +- 725207      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-chromium --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/8970642923641868336


For feedback, file a bug with component Speed>Bisection

mek: ping? The bisect is reproducing a 1.6mib memory regression, which is a lot for android.