Has this been reported to Chromium / WebRTC? At a quick glance I don't see it in the WebRTC bug tracker.