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

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


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

android-nexus9

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

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision                             Mean       Std Dev   N  Good?
chromium@424460                      163119104  13681763  8  good
chromium@424462                      163492659  12321326  5  good
chromium@424462,catapult@840e04295a  211307725  15203674  5  bad
chromium@424463                      202892902  13169442  5  bad
chromium@424464                      211569869  7519010   5  bad
chromium@424467                      209944576  16325700  5  bad
chromium@424473                      201244672  14285549  8  bad
chromium@424486                      210783437  16611948  5  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 655258

Test Command: 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_stress
Test Metric: memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/https_www_google_co_uk_hl_en_q_science
Relative Change: 28.43%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2184
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8998979075788959344


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5869326307950592

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

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean       Std Dev   N    Good?
chromium@424300  168919040  4269408   5    good
chromium@424400  160661504  18227021  5    good
chromium@424450  156368896  17787027  8    good
chromium@424457  168892826  4309858   5    good
chromium@424460  166533530  3576849   5    good
chromium@424462  207430490  15043956  210  good
chromium@424475  201981952  19450175  8    bad
chromium@424500  210311578  4742561   5    bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 655258

Test Command: 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_stress
Test Metric: memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/https_www_google_co_uk_hl_en_q_science
Relative Change: 24.50%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2219
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997725868688707536


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5032063873318912

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

Only N9s. WontFix.

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

=== 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_nexus9_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/https_www_google_co_uk_hl_en_q_science

Suspected Commit Range
  1 commits in range
  https://chromium.googlesource.com/chromium/src/+log/5b99bb23039bb2457a509282f8fc9b839072ca8a..62dc3ff33032432888e0f08a2915df0e88b7c19d


Revision             Result                     N
chromium@424300      168919040 +- 4269408       5        good
chromium@424400      160661504 +- 18227021      5        good
chromium@424450      156368896 +- 17787027      8        good
chromium@424457      168892826 +- 4309858       5        good
chromium@424460      166533530 +- 3576849       5        good
chromium@424462      207430490 +- 15043956      210      good
chromium@424475      201981952 +- 19450175      8        bad
chromium@424500      210311578 +- 4742561       5        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_stress

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

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


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