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

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


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

android-nexus6

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science


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

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

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


| 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 Speed>Bisection.  Thank you!

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science


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

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

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


| 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 Speed>Bisection.  Thank you!

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

=== BISECT JOB RESULTS ===
Bisect failed unexpectedly

Bisect was aborted with the following:
  Step('Check bisect finished on revision chromium@475334.Expanding revision range for revision 74b683277b61ca81642c76386de81200860a12f1 on depot v8') failed with return_code 1


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science

Revision             Result                  N
chromium@475304      6209609 +- 10211.7      5       good
chromium@475322      6223518 +- 42837.3      6       good
chromium@475331      6207814 +- 52980.3      9       good
chromium@475333      6214871 +- 49638.5      9       good
chromium@475334      6390082 +- 124256       6       bad
chromium@475335      6376189 +- 397694       14      bad
chromium@475339      6384271 +- 188042       9       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

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

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


| 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 Speed>Bisection.  Thank you!

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

=== BISECT JOB RESULTS ===
Bisect failed unexpectedly

Bisect was aborted with the following:
  Step('Check bisect finished on revision chromium@475334.Expanding revision range for revision 74b683277b61ca81642c76386de81200860a12f1 on depot v8') failed with return_code 1


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science

Revision             Result                  N
chromium@475304      6209609 +- 10211.7      5       good
chromium@475322      6223518 +- 42837.3      6       good
chromium@475331      6207814 +- 52980.3      9       good
chromium@475333      6214871 +- 49638.5      9       good
chromium@475334      6390082 +- 124256       6       bad
chromium@475335      6376189 +- 397694       14      bad
chromium@475339      6384271 +- 188042       9       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

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

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


| 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 Speed>Bisection.  Thank you!

This is only a 160kib regression, looks like it's from the v8 roll in r475334, but after two months it seems unlikely we'll track down and fix.