fix(playerdatastorage): Explicitly set _instance to null to avoid double release #902
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
WispyMouse
requested review from
andrew-hirata-playeveryware,
arthur740212 and
paulhazen
paulhazen
approved these changes
Sep 11, 2024
arthur740212
approved these changes
Sep 11, 2024
andrew-hirata-playeveryware
approved these changes
Sep 11, 2024
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.
The
Releasemethod is being called directly in some places for the wrapper. If you try to Release a EOS notification handle that has already been released, it crashes Unity. This safely sets the _instance to null after releasing, to make sure that doesn't happen again.