Hi, We’ve recently been investigating memory usage of our iOS app, and discovered that when using the CBLManager sharedInstance, opening lots of databases, and then closing them (releasing the refs to them), the SQLite page cache memory is not released for those previously opened databases. We have observed this by watching memory usage in Instruments.
One of my colleagues reported that when constructing our own instance of CBLManager, releasing the refs on the databases would cause the SQLite page cache to release the associated memory for those databases. As I write this, I’m not sure if our CBLManager instance was also released in order to recover the memory (I’ll try to find out - but he’s currently on vacation). We’d like to know if this sounds familiar, or is unexpected. Is the answer to simply use our own CBLManager instance? I ask, because it seems like a bad idea for the sharedInstance to never release this memory, and I’m wondering if that’s just a bug that needs fixing. Thanks, -Todd -- 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/9e32060a-3c10-4812-83ee-97d683984dd7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
