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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDglo7LogoM


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

chromium-rel-win7-gpu-nvidia

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

=== Auto-CCing suspected CL author alexclarke@chromium.org ===

Hi alexclarke@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Alex Clarke
  Commit : cfd4fb5bd56f9e0f98668471a21f7f720cd5c311
  Date   : Thu Jun 08 10:26:12 2017
  Subject: Pause virtual time until provisional navigations are committed

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_search/load_search_yandex
  Change       : 9.49% | 11667228.4444 -> 12715804.4444

Revision             Result                   N
chromium@477898      11667228 +- 1782236      9       good
chromium@477918      11550720 +- 1482910      9       good
chromium@477928      11887762 +- 2298169      14      good
chromium@477933      11638101 +- 882508       6       good
chromium@477934      11550720 +- 0.0          6       good
chromium@477935      12599296 +- 0.0          6       bad       <--
chromium@477937      12715804 +- 653902       9       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.search.yandex system_health.memory_desktop

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8977233055952118080

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5775969241006080


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

Issue 731662 has been merged into this issue.

 Issue 731707  has been merged into this issue.

 Issue 732297  has been merged into this issue.

 Issue 732296  has been merged into this issue.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/fd98b65e68c329ff0bb43db5a1c15e50aaa6c66d

commit fd98b65e68c329ff0bb43db5a1c15e50aaa6c66d
Author: Alex Clarke <alexclarke@chromium.org>
Date: Tue Jun 13 15:44:08 2017

Fix logic to flush internal scheduler state on navigation comit.

Fixes a bug introduced by https://chromium-review.googlesource.com/522069

Bug:  731880 
Change-Id: I3035987c467dfe31c32d72b37beafc62a4d391b8
Reviewed-on: https://chromium-review.googlesource.com/532902
Reviewed-by: Alexander Timin <altimin@chromium.org>
Commit-Queue: Alex Clarke <alexclarke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#479030}
[modify] https://crrev.com/fd98b65e68c329ff0bb43db5a1c15e50aaa6c66d/third_party/WebKit/Source/platform/scheduler/renderer/renderer_scheduler_impl.cc
[modify] https://crrev.com/fd98b65e68c329ff0bb43db5a1c15e50aaa6c66d/third_party/WebKit/Source/platform/scheduler/renderer/renderer_scheduler_impl_unittest.cc
[modify] https://crrev.com/fd98b65e68c329ff0bb43db5a1c15e50aaa6c66d/third_party/WebKit/Source/platform/scheduler/renderer/web_view_scheduler_impl.cc

 Issue 732810  has been merged into this issue.

Issue 733112 has been merged into this issue.

Issue 733112 has been merged into this issue.

Issue 733112 has been merged into this issue.