* fixed: #684 -- crash on GC when releasing object that fails to init
#686
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
…o `init` root case: when init return nil -- it calls `-release` on allocated object. but objc code was keeping old handle returned by `+alloc`. as result when Java object with this handle was disposed by GC -- it was calling `-release` on this zombie handle that caused EXC_BAD_ACCESS
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.
root case
when init return nil -- it calls
-releaseon allocated object. but objc code was keeping old handle returned by+alloc. as result when Java object with this handle was disposed by GC -- it was calling-releaseon this zombie handle that caused EXC_BAD_ACCESS