Issue metadata
Sign in to add a comment
|
Peer connection drops/fails intermittently on 67.0.3381.0
Reported by
thehunmo...@gmail.com,
Mar 30 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3381.0 Safari/537.36 Steps to reproduce the problem: 1. Establish connection as a publisher/subscriber 2. Open a private browsing tab, open a second publisher/subscriber connection What is the expected behavior? The peer connection videos are displayed correctly. What went wrong? The peer connection videos succeed and are displayed initially, but then quickly disappear. Did this work before? Yes Version 66.0.3359.66 Does this work in other browsers? Yes Chrome version: 67.0.3381.0 Channel: dev OS Version: OS X 10.12.6 Flash Version: In the demo videos, the video on the left is simply local video display, the video on the right is a peer connection. I performed the exact same test on Chrome Dev 67 and Chrome Beta 66 (and also previously on Chrome Stable 65), and everything works fine on Stable and Beta, but the video fails to display after initial connection on Chrome Dev 67. I don't see anything on quick inspection of the attached WebRTC dump files, the ICE connections in both cases seem to all complete successfully. The app I'm using is one I've written and maintain. I've made no changes to it in months. It's available at https://connect.circleanywhere.com/event/585, and is access protected, but I can provide access if needed. I test this app regularly on the Dev channel, and recently this failure started happening. Happy to provide other debugging stuff if necessary, and/or run other tests.
,
Mar 30 2018
,
Mar 30 2018
Thanks for filing the issue! @Reporter: Could you please help us in confirming whether this issue is similar to that of Issue 826972 which even speaks about Peer connection(WebRTC). CC'ing Steve Anton from Issue 826972 for more inputs on this issue.
,
Mar 30 2018
No, I don't think this is related to Issue 826972 .
,
Apr 1 2018
I've looked at https://bugs.chromium.org/p/chromium/issues/detail?id=826972 and agree with @steveanton that this issue is not related.
,
Apr 1 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 2 2018
Thanks for your confirmation Steve Anton and thehunmonkgroup. Checked the issue on chrome version 67.0.3386.0 using Mac 10.13.1 with the below mentioned steps. 1. Launched chrome 2. Navigated to https://connect.circleanywhere.com/events/ 3. Clicked on Sign up -> Let's go 4. logged in using Google account. It resulted to a payment page for membership options. @thehunmonkgroup: Could you please share sample test credentials which helps us to triage the issue in a better way. Any further inputs from your end may help us. Thanks!
,
Apr 3 2018
My apologies, I've set up some test credentials and detailed steps below so you can reproduce. I've tried to streamline the process as much as possible. Note that, unfortunately, the problem seems intermittent -- what I can say with a high degree of confidence is that it does *not* occur on Chrome 65 Stable and Chrome 66 Beta, and does occur intermittently on Chrome 67 Dev. Test login credentials: chromium.1.stirlab@gmail.com 8Hx&Q0m$HL6@U6V3Peql chromium.2.stirlab@gmail.com ziB675j8N%MHyDtBXgOe Steps: 1. Open regular Chrome browsing session 2. Visit https://connect.circleanywhere.com/event/chromium-testing 3. Log in with the chromium.1.stirlab user 4. Complete the brief audio/video configuration/connectivity test 5. Open private Chrome browsing session 6. Repeat steps 2-4, this time logging in with the chromium.2.stirlab user 7. In each open app window, once the display has fully loaded, click the green 'JOIN' button 8. Observe that the subscribed feed (right side) successfully connects, then immediately disappears on Chrome 67 Dev, but works fine for Chrome 65 Stable and Chrome 66 Beta Please let me know if you need any more information, I'm happy to help with debugging/etc.
,
Apr 3 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 4 2018
,
Apr 4 2018
,
Apr 4 2018
Unable to reproduce the issue on reported chrome version 67.0.3381.0 and on the latest Dev 67.0.3386.1 using Mac 10.12.6 with the below mentioned steps. 1. Launched Chrome 2. Navigated to https://connect.circleanywhere.com/event/chromium-testing 3. Entered the credentials given in comment#8 4. completed configuration/connectivity test. 5. Opened an incognito window and performed steps 2 and 3 with the second credentials given. 6. After it's fully loaded clicked Join. We didn't find any connection drop/fail. Attaching the screen cast of the same. @thehunmonkgroup: Could you please have a look at the screen cast and let us know if we have missed anything. As the issue isn't seen even in latest Dev, could you please check the same on it. You can download latest chrome versions from below link. https://www.chromium.org/getting-involved/dev-channel Thanks!
,
Apr 27 2018
As of 68.0.3409.2 this no longer appears to be an issue. Feel free to close.
,
Apr 27 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 30 2018
As the issue seems to be resolved(i.e., from Comment#13) hence removing Needs-Bisect label and closing the issue, marking it as Won't fix. . Thanks! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by viswa.karala@chromium.org
, Mar 30 2018