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

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


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

android-nexus6
android-nexus7v2

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

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

Suspected Commit
  Author : Ulan Degenbaev
  Commit : 774a4c5e240569b551cc9d19ae8cac146891d4c4
  Date   : Fri Jul 28 19:42:31 2017
  Subject: Revert "[heap] Reland "[heap] Allow a minimum semi-space size of 512K.""

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_games/load_games_bubbles
  Change       : 9.36% | 6932624.66667 -> 7581231.33333

Revision                           Result                  N
chromium@490643                    6932625 +- 25867.1      6      good
chromium@490649                    6932385 +- 56775.6      6      good
chromium@490652                    6936698 +- 64575.2      6      good
chromium@490652,v8@59ddd6061c      6928014 +- 44525.7      6      good
chromium@490652,v8@e567dd3ab4      6945035 +- 37069.0      6      good
chromium@490652,v8@774a4c5e24      7610389 +- 114454       6      bad       <--
chromium@490652,v8@4a9718c777      7594851 +- 126992       6      bad
chromium@490653                    7599540 +- 60692.1      6      bad
chromium@490654                    7604513 +- 78673.2      6      bad
chromium@490655                    7611457 +- 138809       6      bad
chromium@490667                    7581231 +- 74937.2      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=load.games.bubbles 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/8972283254229439584


For feedback, file a bug with component Speed>Bisection