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

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


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

android-nexus7v2

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3390
Failure reason: the build has failed due to infrastructure failure.

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

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4292
Failure reason: the build has failed due to infrastructure failure.

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N   Good?
chromium@424400  22994350  1209729  18  good
chromium@424600  23151762  2858192  18  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 655265

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=http.search.yahoo.com.search..ylt.p.google memory.top_10_mobile_stress
Test Metric: memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/foreground/http_search_yahoo_com_search__ylt_p_google
Relative Change: 0.92%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4293
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997727215399175744


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

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

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

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


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev   N   Good?
chromium@424532  23073873  11707593  21  good
chromium@424578  24025559  14793052  21  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 655265

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=http.search.yahoo.com.search..ylt.p.google memory.top_10_mobile_stress
Test Metric: memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/foreground/http_search_yahoo_com_search__ylt_p_google
Relative Change: 4.12%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4467
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993073480547729552


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

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

===== BISECT JOB RESULTS =====
Status: completed


===== TESTED REVISIONS =====
Revision         Mean      Std Dev   N   Good?
chromium@422806  34345357  1070141   6   good
chromium@423674  34201087  1677155   9   good
chromium@424108  35756154  12574207  9   good
chromium@424325  34216992  1138688   6   good
chromium@424434  34668917  1671409   9   good
chromium@424461  37405728  20451774  14  good
chromium@424462  34689397  1326885   6   good
chromium@424463  46778969  6847636   9   bad
chromium@424465  47715588  5361613   9   bad
chromium@424468  46854907  9375825   14  bad
chromium@424475  46887675  8445663   14  bad
chromium@424488  46562336  6247615   9   bad
chromium@424542  45915168  3287943   9   bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 655265

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:system_memory:private_dirty_size_avg/foreground/https_www_google_co_uk_hl_en_q_science
Relative Change: 35.21%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3567
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993073489367478848


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

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

Looks like it was the catapult roll:
https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/a1fdeaa2c402..840e04295a00

Ned or Dave, could either of your changes have changed how long the page runs for enough to have caused a big memory use change?

My change is about error handling, so it's more likely that Bokan change that cause this memory use change. Though that change should make the test more realistic.

Right, it's likely my patch in that case. I'm guessing that waiting the extra frame allows more loading to take place and so more memory is recorded.

Mark this is WAI then.