You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a about 20 documents that usually carry about 30 attachments that are about 5MB's each. I started noticing that the replication on app start up never goes back to idle, it gets stuck in active indefinitely. The effects of this is that I never know when the replicator is done, and also going from foreground to background and vice-versa causes the app to freeze because the replicator is trying to suspend but it can't so locks the main thread. Actually, I can never stop the replicator because it's waiting for database endlessly.
Below are my logs. This has happened with sever accounts, but not at first. Once they start gathering more attachments it seems. I have a log for the same user that starts up the app twice. My point of both logs is I wanted to show that no data was changed on client or server, but gets stuck replicating.
Why are attachments causing the replicator to never get to idle?
Version: Couchbase Lite 1.3.1 (build 6) (master branch, Aug 26 2016)
I have a about 20 documents that usually carry about 30 attachments that are about 5MB's each. I started noticing that the replication on app start up never goes back to idle, it gets stuck in active indefinitely. The effects of this is that I never know when the replicator is done, and also going from foreground to background and vice-versa causes the app to freeze because the replicator is trying to suspend but it can't so locks the main thread. Actually, I can never stop the replicator because it's waiting for database endlessly.
Below are my logs. This has happened with sever accounts, but not at first. Once they start gathering more attachments it seems. I have a log for the same user that starts up the app twice. My point of both logs is I wanted to show that no data was changed on client or server, but gets stuck replicating.
Why are attachments causing the replicator to never get to idle?
On app startup:
Restart the app a few seconds later with no data changes made on client or server:
The text was updated successfully, but these errors were encountered: