-
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 in CBLBatcher #187
Comments
I got a nearly-identical crash report via email from JV this morning, too. Looks like in the |
Also, note to self: The batcher here is CBLPuller's |
For what it's worth, it happened when I stopped a quite large, non-continuous, non-persistent pull replication soon after starting it (~2-3 seconds). But ironically enough, I can't replicate it. |
I'm seeing this one also. Well, it came in as a Crashlytics crash report from one of our pre-release users. Didn't actually see it myself. Here's a copy/paste from the Crashlytics report:
|
Still seeing this issue.
|
Here's the relevant log: We have an active pull replication started, and then start another one. On occasion, this fails, but not 100%. It's often enough that it's a problem, though. :) |
The -stop method can end up being called re-entrantly, and it wasn’t expecting that, so Bad Stuff could happen. Also made the CBLReplicator’s -stop method simply clear the batcher instead of flushing it, since any queued changes in it shouldn’t be processed anyway (they’d result in remote requests that would just immediately be stopped.) For #187, #191, #193
Looks fixed in commit b834d56 "Fix problems stopping a replicator". Thanks! |
Whew! |
The text was updated successfully, but these errors were encountered: