framesDecoded is not incrementing when streaming in Chrome Canary and Beta
Reported by
ja...@tokbox.com,
Dec 22 2016
|
|||||||
Issue descriptionChrome Version: <From about:version: Google Chrome 57, 56> Chrome OS Version: <From about:version: Platform 56,56> Chrome OS Platform: <Mac OS Sira> <b>Network info: <network, encryption type, router model (if known)></b> our webrtc video communication app freezes and unfreezes when we change the stream widget different streams. I did notice that the SSRC framesDecoded getStats value stops incrementing upwards during the freeze,This happens in chrome canary and beta, not happening in stable. Steps To Reproduce: (1) Join our webrtc video streaming session. for example: meet.tokbox.com/google (2) Join the session with 3-4 streams (3)Double click streams randomly, wait for 2-3 seconds between layout change (4) check webrtc internals, framesDecoded should be incrementing steadily Expected Result: nothing is frozen Actual Result: Streams get randomly freeze when you change the stream widget How frequently does this problem reproduce? sometimes What is the impact to the user, and is there a workaround? If so, what is it? There is no workaround at this point. This will impact our user experience with the app. Please provide any additional information below. Attach a screen shot or log if possible. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Nov 3 2017
,
Nov 6 2017
,
Nov 6 2017
Not familiar with webrtc internals - assigning to WebRTC component for the right folks to take a look. FWIW, I was also not able to reproduce any freezing on my Mac (Sierra + Canary). I had 3 streams going, but found that double clicking the videos didn't cause a significant layout change (the maximize icon would toggle, but video remained in the same spot).
,
Jan 18 2018
Ping for triaging.
,
Apr 26 2018
Ping.
,
May 1 2018
Removing self, adding WebRTC chrome expert. Please triage.
,
May 2 2018
james@: Is this still an issue?
,
May 2 2018
,
Aug 17
Archiving since there is not enough actionable data and the bug refers to a very old Chrome version. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by vsu...@chromium.org
, Nov 3 2017