[bug] remove finalClose from SQLCipherU1DBSync

We discovered that class was registering a `finalClose` to be
executed on reactor shutdown.

On the multiuser scenario, a logout destroys Soledad and should
properly terminate everything related to it. That SQLCipherU1DBSync
instance was being held even after logout by the reactor so it
could call that `finalClose` on shutdown.

The `finalClose` only set running to False and set a `shutdownID` that
was not used anywhere else, so we removed it and moved setting
running to False to the `close` function method. That way we preserve
the functionality but let the instance be properly garbage collected
on logout.

0 files changed, 0 insertions, 0 deletions