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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgsMjXsgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0NuRvgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0K_MqQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0KaqugkM


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

android-nexus6
android-nexus7v2

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/background/after_http_search_yahoo_com_search__ylt_p_google
  Change       : 1.17% | 75185232.0 -> 75800144.0

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/30abd07e271e93f99b70745a08b360793be779cc..9079de0121eb747464e490e29fd2444dde5f0847


Revision             Result                   N
chromium@445507      75185232 +- 1887584      14       good
chromium@445508      ---                      ---      build failure
chromium@445509      75745726 +- 1594405      14       bad
chromium@445511      75711836 +- 1976047      21       bad
chromium@445515      75803947 +- 1525879      14       bad
chromium@445523      75899813 +- 3019799      21       bad
chromium@445539      76014160 +- 1900360      14       bad
chromium@445570      75800144 +- 730733       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=http.search.yahoo.com.search..ylt.p.google memory.top_10_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8989487087331734320

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5901662318755840


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

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

Nothing in range looks plausible - starting new bisect.

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

Suspected Commit
  Author : bcwhite
  Commit : ba68aeb47c44cb7ccc9b1e1cab35cc032556dfe6
  Date   : Mon Jan 23 22:30:51 2017
  Subject: Make MappedFile (aka OnDisk) the default for persistent histograms.

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/background/after_http_www_baidu_com_s_word_google
  Change       : 0.77% | 80164627.0476 -> 80784878.4762

Revision             Result                   N
chromium@445507      80164627 +- 2582758      21      good
chromium@445515      80191966 +- 1330955      9       good
chromium@445516      80832763 +- 1055904      9       bad       <--
chromium@445517      80886921 +- 994893       9       bad
chromium@445519      80944062 +- 2240492      14      bad
chromium@445523      81008777 +- 1851785      9       bad
chromium@445539      80791234 +- 1225536      9       bad
chromium@445570      80784878 +- 2351972      21      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=http.www.baidu.com.s.word.google memory.top_10_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8989471541046879168

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6160766689869824


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!