| commit | 7dc6a57d65d415ea3d873c562616ca81bbcb3694 | [log] [tgz] |
|---|---|---|
| author | sangheon77.kim <sangheon77.kim@samsung.com> | Tue May 24 12:59:29 2022 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 24 12:59:29 2022 |
| tree | f74afc87c0c7c9204fc97dcb6d1e99be411a8d0b | |
| parent | 75220033b79ce3e584e5010311e09cecf8acafba [diff] |
Reset current frame of video provider when context is lost When user switch to another applicaiton during user is using browser, system LMK can kill browser's gpu process if other app require memory. This is natural situation in Android. When user goes to HOME, if there was html video in browser's page, video frame's resources are lost when gpu proces is killed. When user return to browser, gpu proces is recreated and context is also recreated. VideoFrameSubmitter start submitting when it receive the new context. But VideoFrameProvider still has current frame which gpu resources are already lost, so VideoFrameSubmitter submitt invalid frame. This invalid frame cause currption on the screen. This patch reset the current frame of VideoFrameProvider when context is lost, so that VideoFrameSumitter will not submit invalid frame. Bug: 1324547 Change-Id: I83e302e16d25fac2f3e6b4a252f13d7b0bce16e3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3642076 Reviewed-by: Stephen McGruer <smcgruer@chromium.org> Reviewed-by: Dale Curtis <dalecurtis@chromium.org> Reviewed-by: Henrik Boström <hbos@chromium.org> Commit-Queue: Sangheon Kim <sangheon77.kim@samsung.com> Reviewed-by: Will Cassella <cassew@chromium.org> Cr-Commit-Position: refs/heads/main@{#1006860}
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.