changing stream codec caused video freezing with the WARNING...dropping frame
Reported by
brightc...@gmail.com,
Jun 10 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/603.1.30 (KHTML, like Gecko) Version/10.1 Safari/603.1.30 Steps to reproduce the problem: 1. reaceive stream from peer 2. change the stream coding type 3. sometimes work, sometimes not What is the expected behavior? Decoding and rending always What went wrong? Video Freezing long time with the many WARNINGs in chrome log such as: WARNING:frame_buffer2.cc Frame with (picture_id:spatial_id) (16132:0) inserted after frame (25704:0) was handed off for decoding, dropping frame Did this work before? N/A Does this work in other browsers? N/A Chrome version: <Copy from: 'about:version'> Channel: n/a OS Version: OS X 10.12.4 Flash Version: Some tolerance has been done in source code of frame_buffer2 such as https://codereview.webrtc.org/2898763005, that's great. but, I think we should also check the frame codec type. If new arrived key frame's codec type is difference from the previous frame, The frame buffer should be cleared as above do.
,
Jun 11 2017
Besides check codec type changing, May there are more other ways?
,
Jun 13 2017
,
Jun 19 2017
,
Jun 19 2017
Brightcove: what codec types are you switching between?
,
Jul 11 2017
It happens to me a very similar issue, related to pictureId. I'm using Licode as SFU (simulcast enabled), and when the receiver switch quality from one spatial layer to another, tons of "(43320:0) has invalid frame references, dropping frame" and the video freezes for 2 to 5 seconds. It happens only from chrome 58, Firefox and older version of chrome never had problems. Also it happens only from a specific spatial layer to another specific spatial layer. Also, it happens occasionally. If the receiver reload the page, the behavior is the same (freezes for seconds). I can reproduce it consistently. But, if the sender reload the page, so it creates a new peerconnection, the problem may disappear, no matter how many switch in spatial layer I do, it works flawlessly. It seems a publisher side problem. Maybe the sfu isn't taking something in consideration, but firefox and old chrome <= 57 never freezes. from 58 to 61 it happens (70% of the times). for a more detailed explanation: https://github.com/lynckia/licode/issues/952#issuecomment-314361387
,
Aug 10 2017
No feedback was received in the last 30 days from reporter "brightcove@gmail.com", so archiving this. Please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||
►
Sign in to add a comment |
|||||
Comment 1 Deleted