[Webkit-unassigned] [Bug 254498] New: [MSE] SourceBufferPrivate and SourceBufferParser should operate in the content process.
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Sun Mar 26 22:31:13 PDT 2023
https://bugs.webkit.org/show_bug.cgi?id=254498
Bug ID: 254498
Summary: [MSE] SourceBufferPrivate and SourceBufferParser
should operate in the content process.
Product: WebKit
Version: WebKit Nightly Build
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: Media
Assignee: webkit-unassigned at lists.webkit.org
Reporter: jean-yves.avenard at apple.com
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.
--
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/20230327/a2833fc6/attachment.htm>
More information about the webkit-unassigned
mailing list