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

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


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

android-nexus5X
android-one
android-webview-nexus6
chromium-rel-mac12

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


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_social/browse_social_pinterest_infinite_scroll

Revision             Result                   N
chromium@499652      21545470 +- 2712417      5       good
chromium@499765      43939511 +- 9864299      12      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.pinterest.infinite.scroll 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/8969101440534579008


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : Eric Karl
  Commit : 6a0f206ccbe0b1e81f53a79f37474a4ba3c760e8
  Date   : Tue Sep 05 20:05:40 2017
  Subject: Use GPU Discardable in Image Decode Cache

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_social/browse_social_tumblr_infinite_scroll
  Change       : 166.77% | 19912896.0 -> 53122493.3333

Revision             Result                    N
chromium@499652      19912896 +- 8305986       8       good
chromium@499709      21677119 +- 1653372       6       good
chromium@499723      21846385 +- 4403985       7       good
chromium@499724      52246112 +- 11598193      6       bad       <--
chromium@499725      54363354 +- 7432423       5       bad
chromium@499727      47471139 +- 9823697       6       bad
chromium@499730      46839464 +- 49491787      13      bad
chromium@499737      50924610 +- 8200835       8       bad
chromium@499765      53122493 +- 12713689      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.tumblr.infinite.scroll 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/8969082275135897808


For feedback, file a bug with component Speed>Bisection