This repository has been archived by the owner on Oct 30, 2018. It is now read-only.
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.
For some yet unknown reasons, registering
UIKeyCommand
objects from withinSLKTextViewController
caused the view controller never to be deallocated, when interacting with at least 1 of these commands on the iPad. Certainly due to a retain cycle since this didn't cause any memory leaks. With the right repro steps, it was possible to get incremental retain cycles.After profiling this for a full day, and looking for different alternatives, I decided to move ALL the key command registration back to
SLKTextView
, using a simpler-to-use API like:Key commands are then registered internally in
SLKTextView
, using a common selector and forwarding the events to the block callbacks. By doing this, the view controller is out of risk from being retained, possibly by a UIKit private object since it was untraceable. It seems to me, that this is a behavior change on UIKit since iOS 9, but unsure.