commit | 7801bbd7a53a86ded23fad7481ba82921454a418 | [log] [tgz] |
---|---|---|
author | Sunny Sachanandani <sunnyps@chromium.org> | Wed Apr 23 20:02:56 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 23 20:02:56 2025 |
tree | 57b4391b054c070601c3abcb048235557ab580e3 | |
parent | 27d3759355ee3b3daa1dd606e5b3a362c04d3723 [diff] |
[gpu] Track IOSurface GL access count separately For SwANGLE, we need to ReleaseTexImage after the last GL access is done to copy from Swiftshader's shadow texture memory to the IOSurface. Today this looks at `num_ongoing_read_accesses_` in the backing, but this is wrong since it considers all kinds of accesses. It's not necessary that the last access being dropped is a GL access so it's possible that the SwANGLE ReleaseTexImage never runs because the last GL access is not the last read access overall. This CL fixes that by tracking a separate `num_ongoing_accesses` in the IOSurfaceBackingEGLState and using that for calling ReleaseTexImage. Additionally, it makes `num_ongoing_read_accesses` a signed int instead of unsigned int so that it's possible to assert that is >= 0 always - we generally want to avoid unsigned types unless it's for serialization or interop with other systems per the style guide. Also, clean up some of the surrounding code a bit and remove a legacy DCHECK from the GLImageBacking days. Bug: 412679361, 40273077, 412679364 Change-Id: Idd06af0a8eef35338934fbddf1a4c8f8cf1af989 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6480226 Auto-Submit: Sunny Sachanandani <sunnyps@chromium.org> Commit-Queue: Saifuddin Hitawala <hitawala@chromium.org> Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org> Reviewed-by: Saifuddin Hitawala <hitawala@chromium.org> Cr-Commit-Position: refs/heads/main@{#1450750}
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.