I have a sample app which displays the behavior. It's very simple, all it does is start continuous push and pull replications. I'd prefer to send it to you instead of posting it here, where should I send it?
Jordan On Monday, January 4, 2016 at 12:38:04 PM UTC-6, Jens Alfke wrote: > > *[Hi! I’m back from vacation. Sorry for the delay.]* I have to say I > start out slightly skeptical of replicator-memory-leak reports because it’s > quite possible for the leak to be caused by application code responding to > the database changes (even if the objects leaked are created by the > replicator; they do get passed via notifications to client code, which can > incorrectly hang onto them.) > > It would be best if you could reproduce the problem using a sample app > like Grocery Sync, by pointing the database URL to your own server/db. That > will confirm it’s the replicator and not your app code. > > —Jens > -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/b58ac9f7-bc63-4102-ab0e-b4720b323bf7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
