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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkLPqswoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0MqgrwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0PKMqQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkImS5AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkPaz4woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0OHW-wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0NzdpQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0OHWuwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkLOMogoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkJfcpAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkP_f8AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0NypuAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0ID25QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0JzvvwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkP_fsAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkPHL8QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0ID25QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0LiKvwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0NGYrQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0MqPpAoM


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

android-nexus5

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

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

Suspected Commit
  Author : Herb Derby
  Commit : 7c5a806bf67e1818b0272a2ae8d854ae1fd72e82
  Date   : Fri Jan 20 17:50:49 2017
  Subject: Move from SkChunkAlloc to SkArenaAlloc for SkGlyphCache.

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science
  Change       : 55.85% | 170592.0 -> 265872.0

Revision                             Result                 N
chromium@445271                      170592 +- 7405.21      6      good
chromium@445274                      169240 +- 0.0          6      good
chromium@445275                      170592 +- 7405.21      6      good
chromium@445275,skia@34c69d6347      170592 +- 7405.21      6      good
chromium@445275,skia@f833215420      169240 +- 0.0          6      good
chromium@445275,skia@abddea0d8c      170592 +- 7405.21      6      good
chromium@445275,skia@7c5a806bf6      265872 +- 0.0          6      bad       <--
chromium@445275,skia@41398f430d      267224 +- 7405.21      6      bad
chromium@445275,skia@aaedae7acb      268576 +- 9366.93      6      bad
chromium@445276                      265872 +- 0.0          6      bad
chromium@445280                      265872 +- 0.0          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.en.m.wikipedia.org.wiki.Science memory.top_10_mobile

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

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


| 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!