[bisq-network/bisq] Bisq using up too much memory on Linux even after closing (#3918)
FKrauss
notifications at github.com
Mon Jan 27 15:14:58 UTC 2020
### Description
Bisq will take more and more memory until the system freezes when none remains.
Additionally if shutdown before no memory is left, not all of it is released. About 4-7GB are shown to be additionally occupied, but no process seems to hold it. Logging out and in again does not fix it. A restart does.
#### Version
1.2.5
### Steps to reproduce
Unknown, just start the application for me.
### Expected behaviour
I expect bisq to take maybe 3GB of ram and released it after closing the application.
### Actual behaviour
More and more ram will be occupied until none is left and the system starts freezing. Sometimes bisq gets terminated by the system other times I just force reboot.
#### Device or machine
Ubuntu 18.04.3
Ryzen 5 2600X
G.Skill Aegis DIMM Kit 16GB
#### Additional info
The log contains a case where, after a reboot I started Bisq and got lucky. The application got terminated (I reacted too slow and could no longer move the mouse) after the ram was full. About 5.5GB of ram were shown to be still occupied after the termination.
[bisq.log](https://github.com/bisq-network/bisq/files/4117738/bisq.log)
--
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/3918
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200127/52c9b79e/attachment.html>
More information about the bisq-github
mailing list