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

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


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

chromium-rel-win10
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win8-dual
linux-release

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/load_games/load_games_lazors
  Change       : 1.14% | 3012200.0 -> 3046688.0

Suspected Commit Range
  9 commits in range
  https://chromium.googlesource.com/chromium/src/+log/d6a190b042fb9dfe980fae5e3a5d8ed62b7605fd..a4b3c363967cb68a7d68a06545c6131c4d4a7171


Revision             Result              N
chromium@489272      3012200 +- 0.0      6        good
chromium@489292      3012200 +- 0.0      6        good
chromium@489296      3012200 +- 0.0      6        good
chromium@489297      3012200 +- 0.0      6        good
chromium@489298      ---                 ---      build failure
chromium@489299      ---                 ---      build failure
chromium@489300      ---                 ---      build failure
chromium@489301      ---                 ---      build failure
chromium@489302      ---                 ---      build failure
chromium@489303      ---                 ---      build failure
chromium@489304      ---                 ---      build failure
chromium@489305      ---                 ---      build failure
chromium@489306      3046688 +- 0.0      6        bad
chromium@489311      3046688 +- 0.0      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=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.games.lazors system_health.memory_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8972265003310318688


For feedback, file a bug with component Speed>Bisection

Regression is small and bisect cannot find the culprit due to build failures.