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

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


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

chromium-rel-win7-gpu-nvidia

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

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

Hi hpayer@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : Fix wrong state of IsolateInBackgroundNotification and IsolateInForegroundNotification.
Author  : hpayer
Commit description:
  
BUG= chromium:636368 , chromium:635965 , chromium:634900 

Review-Url: https://codereview.chromium.org/2245483004
Cr-Commit-Position: refs/heads/master@{#38598}
Commit  : b992a8e1899091e3c180a050c1a63fa1e29886d5
Date    : Fri Aug 12 08:13:56 2016


===== TESTED REVISIONS =====
Revision                       Mean      Std Dev    N  Good?
chromium@411585                0.837151  0.137361   5  good
chromium@411591                0.828167  0.10309    8  good
chromium@411592                0.820026  0.100996   8  good
chromium@411592,v8@64658b6c28  0.81923   0.0516068  5  good
chromium@411592,v8@e6e32315cc  0.840817  0.0583967  5  good
chromium@411592,v8@b992a8e189  1.05432   0.0456413  5  bad    <--
chromium@411593                1.11012   0.163434   8  bad
chromium@411594                1.11615   0.157347   5  bad
chromium@411596                1.09812   0.100134   5  bad
chromium@411607                1.06523   0.0649234  5  bad

Bisect job ran on: winx64nvidia_perf_bisect
Bug ID: 638006

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests memory.long_running_idle_gmail_background_tbmv2
Test Metric: v8-gc-total_avg/v8-gc-total_avg
Relative Change: 27.25%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1806
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004219925723777520


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

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

 Issue 638007  has been merged into this issue.

 Issue 638008  has been merged into this issue.

 Issue 638009  has been merged into this issue.

This CL fixed a bug and restored the original score, c.f. all graphs went back up to where they were before.