Bug 254498 - [MSE] SourceBufferPrivate and SourceBufferParser should operate in the content process.
Summary: [MSE] SourceBufferPrivate and SourceBufferParser should operate in the conten...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Media (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2023-03-26 22:31 PDT by Jean-Yves Avenard [:jya]
Modified: 2023-03-26 22:31 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jean-Yves Avenard [:jya] 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.
Comment 1 Radar WebKit Bug Importer 2023-03-26 22:31:32 PDT 
<rdar://problem/107253559>