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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqPaaoQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqKzaqQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqIzfswoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyNuQswkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyOGGowkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqJievAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqJjApQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqMqjvAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyN-htAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqPnXsAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqMq5rQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqJiKrQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqJi3qwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyN-6pQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyKXgowoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyJWeogoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqKyLtAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqPblqQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqPnDoQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqPK0rAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqPbQrgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqKywoQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyNvPvwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqLa9pgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyMWiuAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqMynvwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyL3GswoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyOXxqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgyP2yvwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgqLbHtwkM


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

android-galaxy-s5
android-nexus5
android-nexus6
android-nexus7v2
android-nexus9
android-one

=== Auto-CCing suspected CL author catapult-deps-roller@chromium.org ===

Hi catapult-deps-roller@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : Roll src/third_party/catapult/ 019f259ae..9f41b8df8 (1 commit).
Author  : catapult-deps-roller
Commit description:
  
https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/019f259ae42a..9f41b8df8242

$ git log 019f259ae..9f41b8df8 --date=short --no-merges --format='%ad %ae %s'

TBR=catapult-sheriff@chromium.org

Review URL: https://codereview.chromium.org/1855283002

Cr-Commit-Position: refs/heads/master@{#384929}
Commit  : 77c38b6f4a211a7290233460c11de6fab439a2ba
Date    : Mon Apr 04 16:53:05 2016


===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@384927         3892.319149 39.541345   6           good
chromium@384928         3883.056896 22.781791   5           good
chromium@384929         6328.338708 157.438988  5           bad         <-
chromium@384930         6399.915396 15.24592    5           bad
chromium@384932         6399.845688 21.942349   5           bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 600708

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests page_cycler.intl_ko_th_vi
Test Metric: cold_times/page_load_time
Relative Change: 63.94%
Score: 99.9

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


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

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

Ned, could the WPR roll have caused more memory usage? https://codereview.chromium.org/1856763002

Filed  bug 600884  on not descending into catapult roll

It's possible but 62% more memory usage is very unexpected.

gabadie@: the wpr change should be a no-op to telemetry since we already have the branching condition to use --ignore-certificate-error on android M+ (https://code.google.com/p/chromium/codesearch#chromium/src/third_party/catapult/telemetry/telemetry/internal/platform/network_controller_backend.py&l=103 & https://code.google.com/p/chromium/codesearch#chromium/src/third_party/catapult/telemetry/telemetry/internal/platform/android_platform_backend.py&l=508)

gentle ping..