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

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


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

chromium-rel-win7-x64-dual

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

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

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/browse_news/browse_news_flipboard

Revision             Result                  N
chromium@492242      20181674 +- 765734      21      good
chromium@492248      20188207 +- 829964      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=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.flipboard 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/8971563465262097952


For feedback, file a bug with component Speed>Bisection

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

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

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/browse_news/browse_news_flipboard

Revision             Result                  N
chromium@492242      20234254 +- 872981      21      good
chromium@492248      20153805 +- 609409      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=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.flipboard 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/8971545203135386368


For feedback, file a bug with component Speed>Bisection

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

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

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/browse_news/browse_news_flipboard

Revision             Result                  N
chromium@492242      20181459 +- 690968      21      good
chromium@492248      20170845 +- 609454      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=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.flipboard 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/8970669693411241440


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : Jakob Kummerow
  Commit : 05e862f78398d8bbeacc7f9e19bbb41c408e709b
  Date   : Fri Aug 04 01:27:42 2017
  Subject: Cache StoreIC-Transition handlers

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/browse_news/browse_news_flipboard
  Change       : 0.93% | 19993256.0 -> 20205524.5714

Revision                           Result                  N
chromium@492045                    19993256 +- 486031      14      good
chromium@492147                    20038638 +- 731596      21      good
chromium@492160                    20010914 +- 608488      14      good
chromium@492161                    19967509 +- 480591      9       good
chromium@492161,v8@5614747680      19996167 +- 357905      9       good
chromium@492161,v8@2fd5e70a03      20010391 +- 656756      14      good
chromium@492161,v8@8b865c8db4      19949405 +- 156619      9       good
chromium@492161,v8@0caf1d2029      20020659 +- 583451      14      good
chromium@492161,v8@05e862f783      20207890 +- 635548      14      bad       <--
chromium@492162                    20215112 +- 418453      9       bad
chromium@492164                    20181071 +- 573173      14      bad
chromium@492167                    20214094 +- 711551      14      bad
chromium@492173                    20253798 +- 624973      14      bad
chromium@492198                    20235009 +- 690080      14      bad
chromium@492248                    20205525 +- 705590      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=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.flipboard 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/8970652580894392016


For feedback, file a bug with component Speed>Bisection