[Webkit-unassigned] [Bug 175185] New: [WebRTC] ICE candidate gathering hangs after reloading page

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Aug 4 04:43:23 PDT 2017


https://bugs.webkit.org/show_bug.cgi?id=175185

            Bug ID: 175185
           Summary: [WebRTC] ICE candidate gathering hangs after reloading
                    page
           Product: WebKit
           Version: Safari Technology Preview
          Hardware: All
                OS: All
            Status: NEW
          Severity: Major
          Priority: P2
         Component: WebCore Misc.
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: andj2223 at gmail.com

Created attachment 317234

  --> https://bugs.webkit.org/attachment.cgi?id=317234&action=review

patch against libwebrtc to enable "immediately start recvonly video upon pageload" behavior.

I've noticed flakiness when refreshing pages that use webrtc in Safari. For example, if the page is set up to automatically start receiving a recvonly video stream, and you repeatedly refresh the page, it will eventually stop working.

To reproduce:
Set up a simple webrtc example that immediately causes a recvonly video stream to be played upon pageload.
Repeatedly refresh the page.

Expectation:
The video stream should start playing upon every single refresh.

Actual result:
After about 4-5 refreshes, safari's progress meter in the url bar will freeze at around the 10% mark, and stay there indefinitely. The page will seemingly never reload.

As mentioned, you do need a simple webrtc example that immediately causes a recvonly video stream to be played upon page load.

If you don't have such an example available to you, you have a couple of options that I know of off the top of my head:

I provide a patch to peerconnection_server/peerconnection_client to have this "recvonly upon pageload" behavior here:
https://bugs.chromium.org/p/webrtc/issues/detail?id=7791
I'm not sure if peerconnection_server/client works with webkit's webrtc, so it may require further changes before using it.

Alternatively, you can use the private url that I provided to Alexey P. and Youenn F. in this bug: 
https://bugs.webkit.org/show_bug.cgi?id=175014
Please get that URL from Alexey or Youenn but do not distribute it outside of webkit/Apple.

Additional notes:
You may be hitting the following issue:
https://bugs.chromium.org/p/chromium/issues/detail?id=725038
(more info) https://bugs.chromium.org/p/webrtc/issues/detail?id=7791
libwebrtc commit 355be367c161 fixes that, which you do not appear to have upon my quick glance (it happened after a87675d4 apparently).

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170804/73d0dc98/attachment.html>


More information about the webkit-unassigned mailing list