Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bisq taking more than 2GB of memory during startup #3430

Closed
BeppeInfo opened this issue Oct 18, 2019 · 10 comments
Closed

Bisq taking more than 2GB of memory during startup #3430

BeppeInfo opened this issue Oct 18, 2019 · 10 comments
Assignees
@freimair
Labels
a:bug an:investigation in:gui is:critical https://bisq.wiki/Critical_bug is:priority PR or issue marked with this label is up for compensation re:usability

Comments

@BeppeInfo
Copy link

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
Copy link

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

@freimair freimair self-assigned this Oct 31, 2019
@BeppeInfo
Copy link
Author

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
Copy link
Contributor

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

Screenshot from 2019-11-25 12-35-09

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?

@freimair freimair mentioned this issue Nov 25, 2019
Closed
@chimp1984
Copy link
Contributor

@freimair Maybe that is related: #3677

@BeppeInfo
Copy link
Author

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

@ripcurlx ripcurlx added is:priority PR or issue marked with this label is up for compensation is:critical https://bisq.wiki/Critical_bug labels Feb 18, 2020
@freimair
Copy link
Contributor

freimair commented Feb 27, 2020 •
edited
Loading

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:
Screenshot from 2020-02-27 12-48-45

@freimair
Copy link
Contributor

freimair commented Feb 27, 2020 •
edited
Loading

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

Bildschirmfoto von 2020-02-27 13-46-24

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

@cbeams cbeams added the a:bug label Feb 27, 2020
@freimair
Copy link
Contributor

@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?

cd2357 added a commit to cd2357/bisq that referenced this issue May 7, 2020
@cd2357
Upgrade JavaFX to v14
e4de859 
Update the gradle dependency to JavaFX 14.

This brings to Bisq the latest JavaFX fixes and improvements, especially
 in the areas of UI performance, memory management and security.

JavaFX can be upgraded independently of the JDK used to build the
application, so this change is modular and does not affect other parts
of the build process.

Related / likely related to: bisq-network#350 bisq-network#2135 bisq-network#2509 bisq-network#3128 bisq-network#3307 bisq-network#3308 bisq-network#3343
bisq-network#3430 bisq-network#3657 bisq-network#3677 bisq-network#3683 bisq-network#3686 bisq-network#3786 bisq-network#3787 bisq-network#3892 bisq-network#3917 bisq-network#3918 bisq-network#3936
@cd2357 cd2357 mentioned this issue May 7, 2020
Closed
@chimp1984
Copy link
Contributor

Can you try out the recommendations at #3918 (comment) ?

cd2357 added a commit to cd2357/bisq that referenced this issue Sep 16, 2020
@cd2357
Upgrade JavaFX to v14
2ce807c 
Update the gradle dependency to JavaFX 14.

This brings to Bisq the latest JavaFX fixes and improvements, especially
 in the areas of UI performance, memory management and security.

JavaFX can be upgraded independently of the JDK used to build the
application, so this change is modular and does not affect other parts
of the build process.

Related / likely related to: bisq-network#350 bisq-network#2135 bisq-network#2509 bisq-network#3128 bisq-network#3307 bisq-network#3308 bisq-network#3343
bisq-network#3430 bisq-network#3657 bisq-network#3677 bisq-network#3683 bisq-network#3686 bisq-network#3786 bisq-network#3787 bisq-network#3892 bisq-network#3917 bisq-network#3918 bisq-network#3936
@ripcurlx ripcurlx mentioned this issue Sep 16, 2020
Closed
6 tasks
@chimp1984 chimp1984 mentioned this issue Dec 13, 2020
Closed
@cd2357
Copy link
Contributor

cd2357 commented May 9, 2021

Should be fixed in the most recent release (v1.6.4) which brings several UI performance improvements and generally reduces system resource consumption (especially RAM). Please try it out and let us know if it's still an issue for you.

@cd2357 cd2357 closed this as completed May 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@freimair freimair

Labels
a:bug an:investigation in:gui is:critical https://bisq.wiki/Critical_bug is:priority PR or issue marked with this label is up for compensation re:usability
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@ripcurlx @cbeams @freimair @BeppeInfo @cd2357 @spogulis @chimp1984