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

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


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

chromium-rel-win10

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

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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/load_news/load_news_qq

Revision             Result                      N
chromium@482966      204927804 +- 218313303      21      good
chromium@483146      213265387 +- 208144438      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=load.news.qq 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/8974805544301220576


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : perezju
  Commit : b4eb70c319cb0f38d1a7764e7d9fb56dc96f8bcf
  Date   : Mon Jun 26 14:25:41 2017
  Subject: [System Health] Extend dump time to 5 seconds

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/load_news/load_news_qq
  Change       : 86.81% | 101515721.333 -> 189640857.333

Revision                                 Result                      N
chromium@482196                          101515721 +- 2309359        6      good
chromium@482256                          101564437 +- 2363579        6      good
chromium@482271                          102463775 +- 3020066        6      good
chromium@482279                          101178245 +- 1922019        6      good
chromium@482281                          101821139 +- 2447075        6      good
chromium@482282                          101904801 +- 2095483        6      good
chromium@482282,catapult@b4eb70c319      230036307 +- 68774725       6      bad       <--
chromium@482283                          158589205 +- 52113485       6      bad
chromium@482286                          209190461 +- 57725105       6      bad
chromium@482315                          195239471 +- 118136069      6      bad
chromium@482434                          199859936 +- 113730730      6      bad
chromium@482671                          204143816 +- 116993974      6      bad
chromium@483146                          189640857 +- 116083412      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_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.news.qq 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/8974748311512701632


For feedback, file a bug with component Speed>Bisection