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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg99quugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgt52ErAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg96SkogkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9_DysQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgt93loQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg99yEoQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg98Da6wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgt8L1vQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgt92vqQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg99jCogsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgt4K3qAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg94SUugsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgt4aPuwsM


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

chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual

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

=== PERF REGRESSION ===


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

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


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


===== SUSPECTED CL(s) =====
Subject : Add function to compute proportional set size for OS_WIN
Author  : chengx
Commit description:
  
Memory-Infra on Windows doesn't use memory usage reported by the OS (proportional set size, private dirty, etc.) yet.

This CL added functionality to calculate proportional set size for a process.

BUG= 623499 

Review-Url: https://codereview.chromium.org/2549803003
Cr-Commit-Position: refs/heads/master@{#437827}
Commit  : b172892773fe15a10508f733ca0bc831240a7ec6
Date    : Mon Dec 12 06:58:22 2016


===== TESTED REVISIONS =====
Revision         Mean       Std Dev   N  Good?
chromium@437823  0.0        0.0       6  good
chromium@437825  0.0        0.0       6  good
chromium@437826  0.0        0.0       6  good
chromium@437827  268139748  34486239  6  bad    <--
chromium@437831  260280052  11352960  6  bad

Bisect job ran on: winx64intel_perf_bisect
Bug ID: 673758

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.long_running_idle_gmail_tbmv2
Test Metric: memory:chrome:renderer_processes:reported_by_os:system_memory:proportional_resident_size_max/memory:chrome:renderer_processes:reported_by_os:system_memory:proportional_resident_size_max
Relative Change: Zero to non-zero

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64intel_perf_bisect/builds/1254
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993379782389305568


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

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

Closing as WAI.  The CL actually fixed the measurement and real results are starting to come in.