Destroy buffers after use, fix bug in BufferTable
#416
Conversation
This file contains 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
Always call `Buffer::destroy()` on the old buffer resource when a GPU buffer is re-allocated. This ensures we get a runtime assertion if a bind group is not recreated and attempt to use a stale buffer. Fix a bug in `BufferTable` where the free list was not updated correctly, which could in theory lead to issues once re-allocating new elements.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Always call
Buffer::destroy()on the old buffer resource when a GPU buffer is re-allocated. This ensures we get a runtime assertion if a bind group is not recreated and attempts to use a stale buffer.Fix a bug in
BufferTablewhere the free list was not updated correctly, which could in theory lead to issues once re-allocating new elements.