Issue metadata
Sign in to add a comment
|
ERR_QUIC_PROTOCOL_ERROR and youtube stream stuttering
Reported by
nipunn1...@gmail.com,
Nov 14 2016
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.87 Safari/537.36 Example URL: Any youtube video. Here is an example https://www.youtube.com/watch?v=fJpp-Uj3c64 Steps to reproduce the problem: 1. Make sure QUIC is enabled. (For me it was set to Default which appeared to be enabled). chrome://flags/#enable-quic 2. Go to a youtube page and play the video. 3. Open up your inspector 4. You'll see that some of the requests fail. These timeout in the 40-45 second time range. In the meanwhile the youtube video fails to make progress and buffer. The failure is a "ERR_QUIC_PROTOCOL_ERROR". The error goes away if you disable QUIC. What is the expected behavior? Smooth streaming. Presumably those failed requests should timeout/retry sooner (or not fail?) What went wrong? Some of youtube's streaming requests fail with ERR_QUIC_PROTOCOL_ERROR causing there to be pauses in the streaming on the order of 30-45 seconds. This does not happen if QUIC is disabled or in other browsers. Did this work before? Yes Not sure Is it a problem with Flash or HTML5? N/A Does this work in other browsers? Yes Chrome version: 54.0.2840.87 Channel: n/a OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 23.0 r0 I posted about this on Facebook and at least 3 other people mentioned having the same problem crop up recently AND the QUIC change fixed it for them. My guess is that it's a regression.
,
Nov 15 2016
Unable to reproduce this scenario, tested in mac 10.12.1 with chrome stable version 53.0.2785.143. These are the steps i followed 1. Opened the google chrome and enable the quic flag and relaunch the chrome. 2. Opened the following url "https://www.youtube.com/watch?v=fJpp-Uj3c64" 3. Opened the developer tools and move to network tab. Observed no errors in the network tab. Please look into the attached screencast and let us know any steps i have missed in executing the scenario. Thank You...
,
Nov 15 2016
Here's a screencast of me running into the issue. Had trouble using the uploader, so here's a Dropbox link. https://www.dropbox.com/s/t34nnkdou8m9t2n/ChromeQUICStreamingBug.mov?dl=0 The only major difference I can see is that I have QUIC set to "default" rather than "enabled". I also probably have a slightly less reliable internet connection (18M down and 3M up), though it's clearly fast enough to stream properly on TCP. Perhaps it drops more packets than yours (which would be a reasonable explanation for a UDP protocol bug). You could try using Network Link Conditioner to simulate different scenarios.
,
Nov 15 2016
I can also point out that I've reproed this problem on two different laptops (both running OSX 10.11.6 and chrome at my home.
,
Nov 15 2016
,
Nov 15 2016
Can you collect a net-internals trace? https://dev.chromium.org/for-testers/providing-network-details
,
Nov 17 2016
,
Nov 24 2016
Thank you for providing more feedback. Adding requester "kkaluri@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
,
Dec 16 2016
,
Mar 13 2017
Cleaning up sheriffbot label "Needs-Review" label as a part of modified "Needs-Feedback" sheriffbot rule. [ref bug for cleanup 684919] |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by dalecur...@chromium.org
, Nov 14 2016