Unpatch D3DResource_Release, detect freeing of resources via DestroyResource instead #1701
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 fixes an issue where host resources and Xbox resources were out-of-sync:
DestroyResource is used internally by the XDK to destroy resources when both the internal and external reference count reach zero,or when the resource is destroyed for any other purpose.
Our D3DDevice_Release was not able to catch all of these situations, leading to incorrect mapping between Xbox and Host resources under certain conditions.