Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix memory access crash #36

Merged
merged 1 commit into from
Sep 14, 2021
Merged

Conversation

mykola-mokhnach
Copy link
Contributor

In general dealloc should never be called explicitly.

@stweil
Copy link
Owner

stweil commented Feb 13, 2019

We don't use automatic garbage collection. How will the object be removed with neither dealloc nor release being called?

@mykola-mokhnach
Copy link
Contributor Author

There is the autorelease pool. Having dealloc there makes the object to be deallocated twice

@stweil stweil merged commit 1826afb into stweil:main Sep 14, 2021
@stweil
Copy link
Owner

stweil commented Sep 14, 2021

@aleksosim reported that this pull request fixes issue #48, so I merged it now. I am sorry that this took so long.

Thank you for the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants