[Webkit-unassigned] [Bug 187136] New: Repeatedly creating PeerConnections results in browser tab freezing

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Jun 27 22:54:12 PDT 2018


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

            Bug ID: 187136
           Summary: Repeatedly creating PeerConnections results in browser
                    tab freezing
           Product: WebKit
           Version: Safari 11
          Hardware: iPhone / iPad
                OS: iOS 11
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebRTC
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: adam at tokbox.com
                CC: youennf at gmail.com

Steps to reproduce:

1. Repeatedly create PeerConnections in Safari on iOS streaming video and audio, over and over again. 

Result: Eventually the browser tab freezes. You see your local video freeze and the remote video freezes. Hitting refresh on the tab seems to hang. You need to close the tab and open a new one.
Or: Sometimes you just get black video after a while. The receiving end just displays black.

I put together a jsbin that reproduces it pretty easily https://output.jsbin.com/haseker

This jsbin establishes an OpenTok Session and subscribes to yourself repeatedly every 1 second. Under the covers this creates 2 PeerConnections, one to send video up to the OpenTok SFU and then one to bring it back down again and display it. It repeatedly creates this second PeerConnection. The timing varies, after about 2-10 minutes of this the browser freezes, or you get the black screen issue. I could not reproduce this issue on Safari on the Mac.

This came up because we had customers complaining that after long running sessions with multiple participants that they were getting a freeze. Also our integration tests which run lots of different tests that create PeerConnections exhibit a similar issue where they hang eventually in Safari on iOS and we can't get through all of them.

-- 
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/20180628/08bfa886/attachment.html>


More information about the webkit-unassigned mailing list