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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgutbT-wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguvGzsQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgusLlvQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2uPbqQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2tP1rwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguuDS4AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2raR8wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguoK9sQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgusSgqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgusDkqQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2uedqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2qOTuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2sO4oAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2ufWowoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgusjo7AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2p3r5AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgus7ksQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgutGftAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgusqSsgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgupWUqQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2uT9jQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2q6BuQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguuymrwsM


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

android-nexus5
android-nexus5X
android-nexus7v2
android-one
android-webview-nexus5X
android-webview-nexus6

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

=== Auto-CCing suspected CL author adamk@chromium.org ===

Hi adamk@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Adam Klein
  Commit : 9397c1b73a607de3c836d9869527cf478668eb19
  Date   : Thu May 18 19:28:58 2017
  Subject: Revert "[parser] Refactor streaming scanner streams."

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_search/load_search_yandex
  Change       : 8.02% | 4981024.0 -> 5380642.0

Revision                           Result                  N
chromium@472979                    4981024 +- 18895.8      6      good
chromium@473033                    4983704 +- 25754.7      6      good
chromium@473047                    4983073 +- 41120.8      6      good
chromium@473051                    4987429 +- 40933.5      6      good
chromium@473053                    4982762 +- 22512.2      6      good
chromium@473053,v8@f4da43618c      4981804 +- 59425.8      6      good
chromium@473053,v8@6b5e443972      4979447 +- 34518.3      6      good
chromium@473053,v8@9397c1b73a      5415275 +- 76189.8      6      bad       <--
chromium@473054                    5419784 +- 110388       6      bad
chromium@473060                    5389399 +- 91932.3      6      bad
chromium@473087                    5395546 +- 86874.9      6      bad
chromium@473195                    5409055 +- 140358       6      bad
chromium@473410                    5380642 +- 137958       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 --story-filter=load.search.yandex system_health.memory_mobile

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

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


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

Not going to ask anyone to unrevert a revert.

 Issue 725007  has been merged into this issue.

 Issue 725952  has been merged into this issue.