Bug 220802

Summary: [GPUProcess][iOS] https://foobar404.github.io/Wave.js/#/ does not output any audio
Product: WebKit Reporter: Chris Dumez <cdumez>
Component: MediaAssignee: Chris Dumez <cdumez>
Status: RESOLVED FIXED    
Severity: Normal CC: eric.carlson, jer.noble, peng.liu6, pvollan, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

Chris Dumez
Reported 2021-01-21 09:34:27 PST
https://foobar404.github.io/Wave.js/#/ does not output any audio when the GPUProcess is enabled (works fine with GPUProcess disabled).
Attachments
Patch (1.60 KB, patch)
2021-01-21 10:32 PST, Chris Dumez 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2021-01-21 09:34:49 PST
<rdar://problem/73455820>
Chris Dumez
Comment 2 2021-01-21 09:39:00 PST
Event though the media file starts playing in the GPUProcess, its current time never changes (stays 0). The media is definitely in PLAYING state, not paused. Interestingly, bypassing RemoteMediaPlayerProxy::setShouldEnableAudioSourceProvider() seems to unblock media playback as I see the current time changing. It must be an issue with the provider somehow.
Chris Dumez
Comment 3 2021-01-21 10:17:56 PST
This is due to sandboxing. Fixing now.
Chris Dumez
Comment 4 2021-01-21 10:32:19 PST
Created attachment 418060 [details] Patch
Per Arne Vollan
Comment 5 2021-01-21 13:36:39 PST
Comment on attachment 418060 [details] Patch R=me.
EWS
Comment 6 2021-01-21 13:39:56 PST
Committed r271711: <https://trac.webkit.org/changeset/271711> All reviewed patches have been landed. Closing bug and clearing flags on attachment 418060 [details].
Note You need to log in before you can comment on or make changes to this bug.