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

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


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

android-nexus6

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

=== BISECT JOB RESULTS ===
NO Perf regression found

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

Revision             Result                 N
chromium@451884      3233050 +- 406587      21      good
chromium@451931      3216925 +- 365150      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 memory.top_10_mobile

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

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


| 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/8986649406026864032

Kicked-off bisect with wider range.

=== 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_nexus6_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_http_m_youtube_com_results_q_science
  Change       : 8.00% | 3249039.55556 -> 3509040.0

Suspected Commit Range
  41 commits in range
  https://chromium.googlesource.com/chromium/src/+log/ec69818af043485daccd4d4f43718390e9ddcb08..e4dd371c464f77b6fbef56d212f7de71e03bf002


Revision             Result                  N
chromium@451800      3249040 +- 346986       9        good
chromium@452000      3226563 +- 166542       6        good
chromium@452027      3198404 +- 14396.7      6        good
chromium@452028      ---                     ---      build failure
---                  ---                     ---      too many build failures to list
chromium@452067      ---                     ---      build failure
chromium@452068      3538564 +- 178671       6        bad
chromium@452100      3562506 +- 72066.3      6        bad
chromium@452200      3509040 +- 229936       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 memory.top_10_mobile

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

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


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

Performance seems to have been restored to normal levels.

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

=== BISECT JOB RESULTS ===
NO Perf regression found

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

Revision             Result                 N
chromium@451884      3293651 +- 711091      21      good
chromium@451931      3223499 +- 401860      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 memory.top_10_mobile

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

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


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