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

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


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

android-nexus7v2

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

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

Suspected Commit
  Author : Benedikt Meurer
  Commit : b9ee0657c6a0b7504d8bf3630e41923d5a72c71f
  Date   : Thu Jul 06 11:55:14 2017
  Subject: [builtins] Unified C++ implementation of Map and Set iterators.

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_games/load_games_lazors
  Change       : 0.90% | 2262769.33333 -> 2283097.33333

Revision                           Result                  N
chromium@484554                    2262769 +- 15215.2      6      good
chromium@484606                    2260007 +- 19273.2      6      good
chromium@484613                    2260007 +- 19273.2      6      good
chromium@484616                    2262803 +- 15252.2      6      good
chromium@484618                    2262769 +- 15215.2      6      good
chromium@484618,v8@124ff5322d      2262781 +- 15227.6      6      good
chromium@484618,v8@b9ee0657c6      2285894 +- 15198.3      6      bad       <--
chromium@484618,v8@b520c6ed5e      2280324 +- 20419.1      6      bad
chromium@484619                    2285871 +- 15277.8      6      bad
chromium@484632                    2283113 +- 19214.2      6      bad
chromium@484658                    2283097 +- 19269.8      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.lazors 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/8974363879136949056


For feedback, file a bug with component Speed>Bisection