[bisq-network/bisq] Bounty for resolving a memory leak issue (#599)

[cd2357]

@robertclarkson: Hmm, then 3 questions:

1. You said you tried out the 1.3.4 deb. Could you paste here the contents of `/opt/Bisq/app/Bisq.cfg` ? More specifically the last 3 sections in that file (JVMOptions, JVMUserOptions and ArgOptions). I'm curious if perhaps due to upgrades from previous versions, somehow an older config file survived with older JVM parameters.

2. When you start Bisq (whichever you prefer, the deb or the snap), the UI will have an indicator bottom left, saying "... Synchronizing DAO" with a sort of moving progressbar. Does that indicator go away after a while (so does "Synchronizing DAO" ever finish)? Or does it keep synchronizing until the 32 GB memory are used up and system hangs?

3. Does this problem with using up all 32 GB of memory + system hanging, does it also happen for a fresh Bisq setup, in other words with a fresh empty data folder? ([Backup your existing data directory](https://docs.bisq.network/backup-recovery.html), then delete the data folder from the original location, and start Bisq. If needed, you can anytime restore your data from this backup.)

-- 
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/issues/599#issuecomment-625727954
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200508/e128a9fb/attachment.html>