layers: Add locks to poison tracking #11113
Merged
+83
−36
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ObjectState can be accessed from multiple threads
Collaborator
|
CI Vulkan-ValidationLayers build queued with queue ID 583060. |
Collaborator
|
CI Vulkan-ValidationLayers build # 21694 running. |
spencer-lunarg
approved these changes
Nov 19, 2025
Collaborator
|
CI Vulkan-ValidationLayers build # 21694 passed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #11102 to work with multiple threads.
Object tracker is designed to be multithreaded without external/global locks, any data strcture that needs sync must implement it. For example, access to ObjectState maps is done via concurrent_unordered_map. Modification of poison tracking structures is done via per object mutex lock.