fix(DataStore): Add 'weak self' to prevent retain cycles in OutgoingMutationQueue #3429
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.
Issue #
#3325
Description
The crash in the issue above points to OutgoingMutationQueue.swift:142
In this PR, we're addressing strong reference cycles in OutgoingMutationQueue by adding
weak self
. Calls toAmplify.DataStore.stop()
will deintialize RemoteSyncEngine, which holds a single instance of the OutgoingMutationQueue. It's likely that OutgoingMutationQueue (self
) is deallocated before one of the closures that have strong reference toself
is executed. Then later, when it executes, it tries to access the deallocatedself
and crashesGeneral Checklist
Given When Then
inline code documentation and are named accordinglytestThing_condition_expectation()
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.