fix: Fix iOS crash/freeze when navigating away #60
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
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
willMoveToWindow:nilgets called when the view gets hidden, e.g. when navigating away. The problem here is, that you can navigate back and the view should be active again, but we completely destroy a reference to it in this method.Instead, we should only destroy the reference in
dealloc.To be a bit more efficient on the CPU we can also think about pausing redraws if
willMoveToWindowgets called with anilwindow and anilsuperview, but deleting the reference just causes the app to crash/the view to freeze and no longer update.