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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgsuTUuQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgsqfrrQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgspXUtwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgsqO6qgsM


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

android-nexus5
android-nexus6
android-nexus7v2
android-nexus9

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


===== SUSPECTED CL(s) =====
Subject : Activate complex text path on Android
Author  : drott
Commit description:
  
In Chromium commit 10749067720a341 catapult was rolled, switching to
default teardowns between pageset repeats, compare [1]. Activating
complex text on Android again after this change in order to see how
measurements are affected by this. If no memory regression shows up in
the memory health measurements for memory pagesets this would indicate
that we may have a memory-leakage over time problem in webview
single-process mode but no issues in the usual tab process lifecycle on
Android. Activating and TBR'ing to collect bot results, potentially
reverting later if needed for further investigation.

[1] https://github.com/catapult-project/catapult/issues/2294

BUG=577306
TBR=eae

Review-Url: https://codereview.chromium.org/2123653005
Cr-Commit-Position: refs/heads/master@{#403884}
Commit  : 5009e3effbb04c74140d262fb71bc51cbf38913a
Date    : Wed Jul 06 11:39:32 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@403879  1445.7   24.4473  5  good
chromium@403882  1445.1   24.9479  8  good
chromium@403883  1450.71  20.687   8  good
chromium@403884  1515.3   47.8857  8  bad    <--
chromium@403885  1511.9   11.086   8  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 627095

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler.top_10_mobile
Test Metric: warm_times/page_load_time
Relative Change: 4.51%
Score: 99.5

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


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

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