Metal: implement more accurate buffer tracking #7839
Merged
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.
This PR updates our Metal buffer tracking logic to use a
NSHashTable
to track alive buffers.NSHashTable
is configured to hold weak references to the buffers we add to it. When a buffer is deallocated, it is automatically removed from the hash table. By counting the number of buffers in the hash table, we get an accurate count of the number of alive buffers.The previous implementation had the limitation that once we pass a buffer off to Metal (when a command buffer becomes the sole owner of it, for example), we assume Metal will eventually release it and and decrement our count. In reality, that buffer could stay alive for a frame or two while the command buffer executes. Using the hash table should give us a more accurate tally of the alive buffer count.