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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg__TzpAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgv6-sqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_62-8ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggNDVpQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_7m9pgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg_7eWoQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgv8ud7QgM


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

chromium-webrtc-rel-win8

You are right that it is caused by https://codereview.chromium.org/2615513003. This is the fix for  issue 677003 . I will merge and mark it as fixed.

goog_avg_encode_ms dropping to 0 shows that HW encoder is used. It is a known problem, see  issue 597087 .