
A service key is generated by `cdm_type`, `browser_context` and `site` in content/browser/media/service_factory.cc. A registered CDM's `cdm_type` will always be a unique non-empty value (i.e. `kMediaFoundationWidevineCdmType`). However, when determining a key systems capabilities, the actual CdmType which corresponds to a Cdm is not used and a default CdmType is used instead. When more than one media foundation cdm is registered, this leads to non-unique ServiceKey's in service_factory.cc when creating the media foundation utility processes which causes different CDM's to use the same utility process and fails when attempting to retrieve the remote media foundation service. Taking CdmType into consideration when querying for key system capabilities addresses the problem. Bug: 394906654 Change-Id: Ie135caf8c06500cf1161ae5c4c1cc687347ba490 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6265506 Reviewed-by: Xiaohan Wang <xhwang@chromium.org> Reviewed-by: Sangbaek Park <sangbaekpark@chromium.org> Commit-Queue: Piet Schouten <Piet.Schouten@microsoft.com> Cr-Commit-Position: refs/heads/main@{#1422064}
Chromium
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead,
follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.