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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzp2T7QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrqz2qgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzv_JmwgM


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

android-nexus5
android-nexus5X
android-nexus6

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

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

Suspected Commit
  Author : khushalsagar
  Commit : de93e30d4aa72f1c1a5c88e2aafba0021697b351
  Date   : Fri Jun 23 23:03:46 2017
  Subject: cc: Move pre-decoding for checkerable images to image worker.

Bisect Details
  Configuration: android_nexus5_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
  Change       : 2.71% | 301706822.667 -> 309888241.333

Revision             Result                    N
chromium@482013      301706823 +- 5006789      6      good
chromium@482039      300237541 +- 7635155      6      good
chromium@482052      301618068 +- 7763923      6      good
chromium@482058      301533076 +- 6793596      6      good
chromium@482061      302159748 +- 7586003      6      good
chromium@482062      309869785 +- 1095356      6      bad       <--
chromium@482063      309699127 +- 1347343      6      bad
chromium@482064      309656825 +- 1119437      6      bad
chromium@482115      309888241 +- 1129972      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.pinterest.infinite.scroll system_health.memory_mobile

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

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


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

Re-opening since this is about a memory regression, and the other bug is about a crash.

khushalsagar: ping? This is a pretty large memory regression, and it does not look recovered.

Sorry I missed this. Will take a look today.