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

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


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

android-nexus5
android-one

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

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

Hi xidachen@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 : Xida Chen
  Commit : ea91b206232bff046594f6f76b547e20c324cc37
  Date   : Wed Sep 06 01:51:20 2017
  Subject: Remove the content feature "ReducedSoftTileMemoryLimitOnLowEndAndroid"

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_news/browse_news_cricbuzz
  Change       : 17.62% | 2592653.77778 -> 3049552.0

Revision             Result                 N
chromium@499765      2592654 +- 570287      9      good
chromium@499822      2545357 +- 583097      9      good
chromium@499836      2543744 +- 643432      6      good
chromium@499843      2570999 +- 329409      6      good
chromium@499844      2990819 +- 406472      6      bad       <--
chromium@499845      3172781 +- 452014      6      bad
chromium@499847      3216445 +- 352383      6      bad
chromium@499850      3157305 +- 416747      6      bad
chromium@499878      3049552 +- 544145      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=browse.news.cricbuzz 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/8968751323201534304


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : Sunny Sachanandani
  Commit : 2eb3c8ac7ffc6840dc07f5e8312576e107eece23
  Date   : Wed Sep 06 02:01:21 2017
  Subject: cc: Flush after every tile task set completes.

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/browse_social/browse_social_instagram
  Change       : 2.01% | 100870826.667 -> 102902442.667

Revision             Result                    N
chromium@499810      100870827 +- 59825.9      6      good
chromium@499839      100936363 +- 494062       6      good
chromium@499843      100947285 +- 487499       6      good
chromium@499844      100958208 +- 274157       6      good
chromium@499845      102957056 +- 470309       6      bad       <--
chromium@499846      102866944 +- 44869.4      6      bad
chromium@499853      102891520 +- 153696       6      bad
chromium@499867      102869675 +- 110314       6      bad
chromium@499923      102902443 +- 75674.5      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=browse.social.instagram 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/8968734473076263296


For feedback, file a bug with component Speed>Bisection