[TreesInViz] Preserve OOM tiles but release existing resource if present. When transitioning a tile to NoContents with MissingTileReason::kOutOfMemory, we now preserve the tile object in the TileDisplayLayerImpl tiling map instead of deleting it. This ensures metadata like tile coordinates and transform are retained for potential future use to do checkerboarding. If the tile previously held a TileResource, the associated GPU resource is explicitly released before updating the tile's contents to reflect the OOM state. This decouples tile lifetime from resource ownership in the OOM case and avoids prematurely deleting OOM tiles that are expected to be deleted later. Bug: 417965009 Change-Id: Ie7b2231d5cb034f5d94fe4ef489c04df83a4ce11 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6554562 Commit-Queue: vikas soni <vikassoni@chromium.org> Reviewed-by: Victor Miura <vmiura@chromium.org> Cr-Commit-Position: refs/heads/main@{#1462595}
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.