[bisq-network/bisq] Optimize DaoState snapshot behaviour (#5609)

[chimp1984]

@chimp1984 commented on this pull request.



> +                // After we have written to disk we remove the reference to the daoState. We have in the meantime
+                // already cloned the next daoState and if we would not release the reference we would have 3 times
+                // the daoState data in memory.
+                store.setDaoState(null);

Yes comment was from earlier version. I updated it in a new commit.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/pull/5609#discussion_r665762294
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210707/ea587dd8/attachment.htm>