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

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


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

android-nexus5

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

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

Hi ssid@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 : Siddhartha
  Commit : 7c9ac4a4e74219b922eec1eef132047470c03e1a
  Date   : Wed Oct 18 03:35:58 2017
  Subject: Add leveldb block cache memory dumps with appropriate sizes

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_news/load_news_wikipedia
  Change       : 3.71% | 21404762.6667 -> 22197978.3333

Revision             Result                   N
chromium@509676      21404763 +- 223443       6      good
chromium@509677      22248996 +- 95251.2      6      bad       <--
chromium@509678      22306480 +- 231563       6      bad
chromium@509679      22236230 +- 102713       6      bad
chromium@509681      22177898 +- 191085       6      bad
chromium@509685      22259997 +- 83501.4      6      bad
chromium@509694      22172102 +- 276617       6      bad
chromium@509712      22197978 +- 120584       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 --story-filter=load.news.wikipedia 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/8965293530854529776


For feedback, file a bug with component Speed>Bisection

ssid@ this is expected, right?

 Issue 776379  has been merged into this issue.

yes, the cl fixes accounting. The regression is expected.

Issue 776790 has been merged into this issue.

Issue 777432 has been merged into this issue.