commit | 8ae33b23132c0920756e6e354e80bc5b9477b424 | [log] [tgz] |
---|---|---|
author | Sangbaek Park <sangbaekpark@chromium.org> | Fri May 12 03:51:54 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 12 03:51:54 2023 |
tree | 82d4f0ac402fadd353cf3660ecdb8a568dbd59b9 | |
parent | 53c3d6fcfe98f501d404e79b4a3eca717b72978a [diff] |
media: Media Foundation Clear Key CDM no rendering image issue fix Fixed the known issue where the test playback never renders image with a sync Media Foundation MFT decryptor once filling out the output data buffer with a sample in the decryptor's ProcessOutput(). See crbug.com/1444893. - Passing `--use-gpu-in-tests` flag when running browser tests is required to render image correctly. - Removed `switches::kDisableGpu` to avoid infinite playback issue with software rendering. See crbug.com/1421444. Build command: ``` autoninja -C out\Default browser_tests .\out\Default\browser_tests --gtest_filter=MediaFoundationEncryptedMediaTest.Playback_ClearLeadEncryptedCencVideo_Success --use-gpu-in-tests .\out\Default\browser_tests --gtest_filter=MediaFoundationEncryptedMediaTest.Playback_ClearLeadEncryptedCbcsVideo_Success --use-gpu-in-tests .\out\Default\browser_tests --gtest_filter=MediaFoundationEncryptedMediaTest.Playback_EncryptedVp9CencAudio_MediaTypeUnsupported --use-gpu-in-tests ``` Bug: 1235887, 1444893 Change-Id: I318eeda938fc7d6293c5a22060537116751be921 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4518497 Reviewed-by: Xiaohan Wang <xhwang@chromium.org> Commit-Queue: Sangbaek Park <sangbaekpark@chromium.org> Cr-Commit-Position: refs/heads/main@{#1143064}
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.