Bug 254498

Summary: [MSE] SourceBufferPrivate and SourceBufferParser should operate in the content process.
Product: WebKit Reporter: Jean-Yves Avenard [:jya] <jean-yves.avenard>
Component: MediaAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   

Jean-Yves Avenard [:jya]
Reported 2023-03-26 22:31:13 PDT
Currently, the SourceBufferPrivate and its SourceBufferParser lives in the GPU Process. This requires extensive back and forth operations between the content and GPU Process, including playing trick so that the MediaSamples that are processed in the GPU Process be owned by the content process. The reasons the SourceBufferPrivate was moved to the GPU Process were historical in that the encryption data if the content was encrypted had to live in the same it was created and played. There are new APIs that remove this restriction.
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2023-03-26 22:31:32 PDT
<rdar://problem/107253559>
Note You need to log in before you can comment on or make changes to this bug.