WebRTC : Delay observed in the video transmission from latest chrome beta
Reported by
kkulka...@bluejeansnet.com,
Aug 12 2016
|
|||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Steps to reproduce the problem: 1. Join the webrtc meeting via latest chrome beta as one end point and chrome stable as the other end point 2. 3. What is the expected behavior? Meeting should should work fine , with very less delay in video transmission from the chrome beta to chrome stable. What went wrong? - There is delay is the video transmission from the chrome beta to chrome stable. - Its taking about 1.06 seconds to transmit a video packet from chrome beta - Tested the same with two chrome stable end points , and delay observed was less Its taking about 600ms to transmit video packets between the two chrome stable variants Hence in the chrome beta there is delay in transmission of the video packets Please find the screen shots of the comparison testing testing done with chrome beta and chrome stable and with chrome stable to chrome stable using the stop watch. Did this work before? Yes The previous windows beta versions it was working fine under the same network conditions Chrome version: 53.0.2785.46 Channel: beta OS Version: 8.1 Flash Version: Shockwave Flash 22.0 r0
,
Aug 22 2016
,
Aug 23 2016
Thanks for the report kkulkarni@. In order for us to debug this further, could you please: 1. Run a test at https://test.webrtc.org/ and then download a report to attach to this bug? (click the bug icon at the top after running the test). 2. Enter chrome://webrtc-internals in a new tab while reproducing this scenario in another tab. Then create a dump and attach here.
,
Aug 23 2016
I have attached the report after running the https://test.webrtc.org/ test . When i ran the test for the first time , some tests got failed. For the failed scenario i have uploaded the logs. Link for the logs uploaded - https://test.webrtc.org/report/AMIfv95pEwaInZd5YmOpgBeKkkcm_EBn7lzyUqFCzucKA0r-jv_h_g2slfZ3A0CxYzgqYxrk_OE3glrlkmo83DuXLsdLJBhzZh3wpwqG1TwRu3C5dor1rNTf_LhLOzI8ttoI_I4TlQf4dsxjuAss9l4utXkYwn6YbA Also , i have taken the dump file but the size of the file more than 10mb and i am not able to upload the file.
,
Aug 23 2016
Adding the test.webrtc.org result file
,
Aug 23 2016
I have managed to upload the webrtc internals dump file also.
,
Aug 25 2016
Observed on the latest chrome beta version 53.0.2785.80 beta as well.
,
Sep 2 2016
Thank you for providing more feedback. Adding requester "kjellander@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 5 2016
[triage] holmer: can you take a look at the attached dumps?
,
Sep 5 2016
,
Sep 5 2016
I can't see anything strange from the webrtc internals dump, all delays look reasonable. I also compared send-side and receive-side delays between M52 Win and M53 Win and I see no significant difference. There was a bit of a difference until early August, so maybe that's what you've been seeing?
,
Sep 6 2016
Issue is not observed on the latest chrome version - 53.0.2785.89 , but there was a delay in the earlier chrome versions
,
Sep 7 2016
Ok, good, then I'll close as "won't fix". |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by l...@bluejeansnet.com
, Aug 16 2016