Repository navigation
vulkan: Remove uninitialized defragLock - #16540
Merged
Merged
Conversation
thatcosmonaut
approved these changes
Oct 17, 2026
Collaborator
|
Merged and cherry-picked, thanks! |
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
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.
Description
The
defragLockin the GPU Vulkan driver was never initialized, so all lock/unlock calls to it were no-ops. Despite this, we haven't had any reports of synchronization issues in the Vulkan backend, so it appears this lock is unnecessary. To prevent confusion when reading the source, I've deleted all references to it.We can of course revisit this if we receive bug reports about race conditions during defragmentation.
Existing Issue(s)
Fixes #16462