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

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


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

chromium-rel-win7-gpu-ati

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

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

===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Fix history nav to a script-injected about:blank frame.
Author  : Charles Reis
Commit description:
  
This CL tracks whether the browser process has an about:blank history
item for subframes during a history navigation.  If the renderer would
be staying on about:blank, it can skip asking the browser and commit
the initial about:blank page synchronously.

BUG= 657896 , 639842
TEST=See bug for repro steps.
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation
R=alexmos@chromium.org

Review URL: https://codereview.chromium.org/2438743005 .

Cr-Commit-Position: refs/heads/master@{#426880}
Commit  : 37c954965f2f221aec294a0a28dfbba1c7543f2a
Date    : Fri Oct 21 20:43:14 2016


===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N  Good?
chromium@426852  31460884  672184   5  good
chromium@426870  31900303  1214063  5  good
chromium@426879  31229214  1295517  5  good
chromium@426880  39263272  2231947  5  bad    <--
chromium@426881  39575879  1988318  5  bad
chromium@426883  39828521  2524775  5  bad
chromium@426887  40854651  1882835  5  bad
chromium@426921  40395243  2752787  5  bad

Bisect job ran on: winx64ati_perf_bisect
Bug ID: 658665

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests system_health.memory_desktop
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/browse_news
Relative Change: 28.40%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64ati_perf_bisect/builds/1624
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997934315060802272


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5774423469064192

| 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 Tests>AutoBisect.  Thank you!

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N   Good?
chromium@426852  39153548  498708   12  good
chromium@426870  39270003  868041   12  good
chromium@426879  39126572  501053   8   good
chromium@426887  40113378  655968   12  bad
chromium@426921  40009737  690930   8   bad

Bisect job ran on: winx64ati_perf_bisect
Bug ID: 658665

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests system_health.memory_desktop
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg
Relative Change: 1.98%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64ati_perf_bisect/builds/1623
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997934341931111568


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5809146937475072

| 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 Tests>AutoBisect.  Thank you!

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