Tear down DBAccess on stopped instead of on release
Description
Related to a reported issue in which a database is unable to be deleted due to our internal classes holding a reference to them. For reasons still unknown, the replicator is not being torn down in a timely fashion which causes this problem. So instead of waiting for it to be torn down before getting rid of the DB handles, do so immediately upon stopped. The class holding these references is designed to be single shot anyway (i.e. if it is needed again after stop, a new one is created) so it doesn't matter much from the class' standpoint where we do this.
Build couchbase-lite-c-3.0.0-170 contains couchbase-lite-core commit 948cab4 with commit message: : Tear down DBAccess on stopped instead of on release (#1293)
CB robot November 23, 2021 at 7:48 PM
Build couchbase-lite-java-3.0.0-183 contains couchbase-lite-core commit 948cab4 with commit message: : Tear down DBAccess on stopped instead of on release (#1293)
CB robot November 23, 2021 at 7:47 PM
Build couchbase-lite-android-3.0.0-182 contains couchbase-lite-core commit 948cab4 with commit message: : Tear down DBAccess on stopped instead of on release (#1293)
CB robot November 17, 2021 at 4:10 AM
Build couchbase-lite-ios-3.0.0-320 contains couchbase-lite-core commit 948cab4 with commit message: : Tear down DBAccess on stopped instead of on release (#1293)
CB robot November 12, 2021 at 5:42 AM
Build couchbase-lite-log-3.0.0-183 contains couchbase-lite-core commit 948cab4 with commit message: : Tear down DBAccess on stopped instead of on release (#1293)
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Related to a reported issue in which a database is unable to be deleted due to our internal classes holding a reference to them. For reasons still unknown, the replicator is not being torn down in a timely fashion which causes this problem. So instead of waiting for it to be torn down before getting rid of the DB handles, do so immediately upon stopped. The class holding these references is designed to be single shot anyway (i.e. if it is needed again after stop, a new one is created) so it doesn't matter much from the class' standpoint where we do this.