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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0OeqtQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgkN-NuAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0KjzkwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0Kja9AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0LO6oQsM


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

chromium-webrtc-rel-7
chromium-webrtc-rel-linux
chromium-webrtc-trunk-tot-rel-linux

hta@ and magjed@: You have been doing changes in H264 code recently. Does anyone of you know if your changes could be related to these regressions?

+philipel@: Could you also please take a look to see whether these may be caused by your recent jitter buffer changes.

This was caused by rollback of the H.264 assembler for encoding in OpenH264. It has been rolled back in.