Bisq: Bisq taking more than 2GB of memory during startup

[AnCaPepe]

I can see that during the syncing to Bitcoin network the Java process listed in my system manager takes more than 2GB of memory, and that doesn't go down after the application is fully initialized

That makes my desktop hang for a long time, as I have only 8GB of RAM here

The operating system is Manjaro KDE x64

[spogulis]

Same on Windows. This is a major flaw for a small app like this one.

[AnCaPepe]

It seems like minimizing the application during startup prevents memory usage from rising that much

Still takes quite a bit of RAM, but my system does not hang

[freimair]

I just ran out of RAM on my dev-machine. 32GB+4GB swap. Here is a visualvm dump of my always-on bisq.

There seems to be a lot of javafx-related stuff taking and keeping a lot of memory. Can anybody investigate the GUI RAM requirements and how to lower them?

[chimp1984]

@freimair Maybe that is related: https://github.com/bisq-network/bisq/issues/3677

[AnCaPepe]

Is that Mesa fix related? https://gitlab.freedesktop.org/mesa/mesa/issues/2270

My personal machine uses radeon graphics with the Mesa drives, but I've saw simular issues in a Nvidia System

[freimair]

hm that is tricky. I, for starters, cannot reproduce the issue - not at all.

My system is a desktop configuration:

• Intel 8th-gen core processor
• plenty of RAM
• Intel Corporation UHD Graphics 630
• Arch linux

here is my first minute of a bisq startup profiled:

[freimair]

and here is the trace with the old trusty laptop

• Intel Core 2 Duo CPU
• 4 GB of RAM
• Nvidia Corporation G98M [Quadro NVS 160M] (rev a1)
• Arch linux

@AnCaPepe can you provide a JProfiler trace like the one's above to document the issue?

[freimair]

@ghubstan had some success with adding -XX:MaxRAM=2147483648 to the java opts and I can confirm that doing that limits the RAM usage to under 2GB, even after days of always-on.

Can you try that?

[chimp1984]

Can you try out the recommendations at https://github.com/bisq-network/bisq/issues/3918#issuecomment-607198677 ?