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

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

Suspected Commit
  Author : Vladimir Levin
  Commit : 47ab7b47d09193a1c924ec9349d541e3a5ed7809
  Date   : Mon Jun 26 20:14:34 2017
  Subject: cc: Used RTree<DrawImage> instead of a separate map of images.

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_social/load_social_twitter
  Change       : 0.21% | 35348533.5 -> 35421886.8333

Revision             Result                   N
chromium@482296      35348534 +- 20124.6      6       good
chromium@482358      35376429 +- 38133.8      9       good
chromium@482366      35382436 +- 47397.8      14      good
chromium@482370      35388258 +- 52451.1      14      good
chromium@482372      35374309 +- 53245.7      6       good
chromium@482373      35421131 +- 38856.2      6       bad       <--
chromium@482374      35422070 +- 124966       14      bad
chromium@482389      35428304 +- 132240       6       bad
chromium@482420      35421887 +- 102820       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.social.twitter 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/8975084827314594512


For feedback, file a bug with component Speed>Bisection