[Webkit-unassigned] [Bug 215964] New: iPad: Audio streams received by WebRTC and fed to Web Audio are killed when switching to another app

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Aug 28 18:46:21 PDT 2020


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

            Bug ID: 215964
           Summary: iPad: Audio streams received by WebRTC and fed to Web
                    Audio are killed when switching to another app
           Product: WebKit
           Version: Other
          Hardware: iPhone / iPad
                OS: iOS 13
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebRTC
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: juberti at google.com
                CC: youennf at gmail.com

Observed on iPadOS14b6, but occurred in earlier iPadOS revs as well.

When receiving an audio stream in WebRTC, and then feeding that stream into createMediaStreamSource, and then connecting that source to AudioContext.destination, this graph gets broken when switching to another app. The context continues as 'running', and the stream is not muted, but all playout stops, and stays stopped even when switching back to Safari.

This does not happen when:
1) WebRTC is fed into an <audio/> element (i.e., no Web Audio)
2) A Web Audio oscillator node is connected to a destination (i.e., no WebRTC)

JSFiddle demonstrating this issue: https://jsfiddle.net/juberti/sr078wyj/
1) Load it up and hit the play button. A tone will start to play out (using WebRTC and Web Audio).
2) Switch to another app. Audio will stop.
3) Switch back to Safari. As seen in the console, the context is still running, but no audio plays out.

-- 
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/20200829/ac83f9d3/attachment-0001.htm>


More information about the webkit-unassigned mailing list