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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmtjU-AgM


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

android-nexus7v2

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/browse_tools/browse_tools_maps

Revision             Result                    N
chromium@469903      112387803 +- 2231749      21      good
chromium@469908      112788041 +- 4788567      21      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.tools.maps system_health.memory_mobile

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

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


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

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/browse_tools/browse_tools_maps

Revision             Result                    N
chromium@469903      112354255 +- 2943801      21      good
chromium@469908      112383122 +- 3018355      21      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.tools.maps system_health.memory_mobile

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

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


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

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

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

Suspected Commit
  Author : ericrk
  Commit : 0fc488920dd2915f5596dda347681e0571bb56dc
  Date   : Mon May 08 17:03:51 2017
  Subject: cc::ResourcePool - Re-use larger resources for smaller requests

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/browse_tools/browse_tools_maps
  Change       : 1.35% | 112332800.0 -> 113435209.143

Revision             Result                    N
chromium@469900      112332800 +- 2120162      14      good
chromium@469968      112758394 +- 4566208      21      good
chromium@470003      112070656 +- 126380       6       good
chromium@470020      112421092 +- 2685621      9       good
chromium@470022      112218112 +- 411072       6       good
chromium@470023      113599829 +- 2208824      6       bad       <--
chromium@470024      113363172 +- 627507       9       bad
chromium@470028      113514268 +- 2287836      9       bad
chromium@470036      113435209 +- 2314083      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=browse.tools.maps system_health.memory_mobile

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

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


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