Fix memory leak of URLSession in SocketEngine #1524
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.
SocketEngine
retains an instance ofURLSession
, and this value is replaced inresetEngine()
. But this instance ofURLSession
is leaked unless you callinvalidateAndCancel()
, which breaks the references between the session and its delegate and callbacks.Note in contrast to other types in Foundation and UIKit,
URLSession
strongly retains its delegate. So the default configuration ofSocketEngine
still has a retain cycle since it sets itself as the delegate of theURLSession
that it owns. Breaking this retain cycle requires user of the library to provide a customURLSessionDelegate
during configuration.