Run SyncService.start()
and stop()
with a non-UI dispatcher
#4133
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.
Content
Run
SyncService.start()
andSyncService.stop()
using a background dispatcher.Motivation and context
The Rust code doesn't seem to handle coroutine cancellation in a nice way, so sometimes when the sync service too a bit longer than expected to run and several syncs tried to start at the same time a deadlock happened which blocked the main thread in Android.
Tests
To make testing easier, since I wasn't able to reproduce this issue on my test devices I built this branch of the SDK to make deadlocks more probable.
Then I opened the app and kept backgrounding it, then opening it back non-stop in short amounts of time: without this patch, I'd have an ANR at 5-6s max. With the patch I couldn't trigger it.
Tested devices
Checklist