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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=851697e9e7ab4c323c2931fa70c4dcaac7b4a45fc8cb97abb391a02cbdb8254c


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

android-nexus7v2

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

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

Hi lpy@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 : Peiyong Lin
  Commit : f50732fbe5cc6fff535adbdee0f9066e1dcc61e7
  Date   : Fri Jul 21 01:59:00 2017
  Subject: Add empty InterfaceProvider for WebFrameClient subclasses.

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_news/load_news_cnn
  Change       : 1.93% | 22192736.0 -> 22612515.5

Revision             Result                  N
chromium@488266      22192736 +- 256519      6       good
chromium@488408      22289746 +- 393847      9       good
chromium@488479      22445736 +- 563595      14      good
chromium@488515      22504850 +- 604488      21      good
chromium@488533      22487023 +- 583019      21      good
chromium@488542      22470711 +- 780105      21      good
chromium@488547      22487587 +- 527228      21      good
chromium@488548      22630408 +- 254594      9       bad       <--
chromium@488549      22601398 +- 384998      14      bad
chromium@488550      22612516 +- 370062      14      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.news.cnn system_health.memory_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8973191565627737376


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : Anton Vayvod
  Commit : 09fa66e1baaa95d069bbd6620670311ae8aa4dc5
  Date   : Thu Jul 20 23:02:12 2017
  Subject: [RemotePlayback] Add media source info to the RemotePlayback availability url

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_news/load_news_cnn
  Change       : 1.44% | 22405884.2222 -> 22728225.8889

Revision             Result                   N
chromium@488266      22405884 +- 1255219      9      good
chromium@488408      22329521 +- 96166.6      6      good
chromium@488446      22282707 +- 178893       6      good
chromium@488463      22269928 +- 183786       6      good
chromium@488464      22154275 +- 169868       6      good
chromium@488465      22546810 +- 224491       6      bad       <--
chromium@488467      22518673 +- 348180       9      bad
chromium@488471      22513417 +- 364622       9      bad
chromium@488479      22562253 +- 157681       6      bad
chromium@488550      22728226 +- 1188694      9      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.news.cnn system_health.memory_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8973167500964005632


For feedback, file a bug with component Speed>Bisection