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

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


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

android-nexus7v2

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

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

Suspected Commit
  Author : Bill Budge
  Commit : 0481b23e2562fcb001494de3765a3ef61427fd00
  Date   : Tue Nov 21 16:48:55 2017
  Subject: [Memory] Rewrite platform OS Commit / Uncommit in terms of permissions.

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/foreground/https_www_google_co_uk_hl_en_q_science
  Change       : 7.06% | 51930526.6667 -> 55595176.0

Revision                           Result                   N
chromium@518572                    51930527 +- 1115690      6      good
chromium@518573                    51658437 +- 1326242      6      good
chromium@518573,v8@a8df8f38a1      52368115 +- 993488       6      good
chromium@518573,v8@8036c41f1e      51813011 +- 749044       6      good
chromium@518573,v8@0481b23e25      55635453 +- 826122       6      bad       <--
chromium@518574                    55689972 +- 1318362      6      bad
chromium@518575                    55901597 +- 1005316      6      bad
chromium@518577                    55370483 +- 676628       6      bad
chromium@518582                    55145203 +- 1440010      6      bad
chromium@518592                    55621021 +- 1967661      6      bad
chromium@518611                    55595176 +- 1790191      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=https.www.google.co.uk.hl.en.q.science 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/8962038227578038432


For feedback, file a bug with component Speed>Bisection