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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgvNeopwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgvJOyrgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_KCsqQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgvMeHvQsM


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

chromium-rel-win10
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia

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

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

Hi littledan@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 : Daniel Ehrenberg
  Commit : dff88c86f61624ad444ff23e2140950c167a7967
  Date   : Fri Apr 07 20:02:20 2017
  Subject: test262 roll

Bisect Details
  Configuration: winx64ati_perf_bisect
  Benchmark    : memory.desktop
  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
  Change       : 3.69% | 5881856.0 -> 6098944.0

Revision                           Result                  N
chromium@462970                    5881856 +- 201996       6      good
chromium@463036                    5782187 +- 200216       6      good
chromium@463069                    5705728 +- 80264.9      6      good
chromium@463078                    5836800 +- 153696       6      good
chromium@463078,v8@749c00ef45      5782187 +- 119652       6      good
chromium@463078,v8@e86d3a2ac6      5804032 +- 227023       6      good
chromium@463078,v8@dff88c86f6      6055253 +- 59825.9      6      bad       <--
chromium@463079                    6077099 +- 144080       6      bad
chromium@463080                    6109867 +- 119652       6      bad
chromium@463082                    6066176 +- 92681.9      6      bad
chromium@463086                    6033408 +- 153696       6      bad
chromium@463102                    6098944 +- 122607       6      bad

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 memory.desktop

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

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


| 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!

This regression appears to have already recovered in all three graphs, gone as abruptly as it came in. I suspect that it was not due to this patch.