-
Notifications
You must be signed in to change notification settings - Fork 298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash during replication #1144
Comments
This is similar to #1015, but in this case it's clearly the CBLRemoteRequest reference that's bad. I think this is actually the same bug, but this time it got a little farther because the (deleted) block variable storage was still accessible memory, and it was able to read a (bogus) CBLRemoteRequest pointer from it. Luca, could you try merging in commit e7d17cb, or at least copying in the change to CBLRemoteRequest.m from that commit? Or you could download the latest nightly build. |
I'm going to close this on the assumption that it's the same bug as #1015. If you still see the problem after getting a fixed build, please comment and I'll reopen it. |
I seem to be observing a similar (if not same) problem, which unfortunately is not fixed by e7d17cb. We have a continuous replication running on iOS. Simply making ANY change remotely will immediately crash the iOS app in this way as soon as the replication attempts to pull down the changes. (An assertion is thrown in It appears as though the Rolling back to CBL 1.1.1 fixes the problem, while 1.2, e7d17cb and current HEAD all seem to be afflicted. |
It seems that this is related to continuous replication. Switching to one-shot appears to avoid the crash, and replication completes as expected. |
During replication I'm getting
EXC_BAD_ACCESS
and app is crashingThis is the log:
The text was updated successfully, but these errors were encountered: