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

Investigate if -BjvmOptions for linux build is still needed #3677

Closed
chimp1984 opened this issue Nov 24, 2019 · 4 comments
Closed

Investigate if -BjvmOptions for linux build is still needed #3677

chimp1984 opened this issue Nov 24, 2019 · 4 comments
Labels
a:bug is:critical https://bisq.wiki/Critical_bug is:priority PR or issue marked with this label is up for compensation on:Linux
Projects
Critical Bugs Board

Comments

@chimp1984
Copy link
Contributor

We added the jvm options -BjvmOptions=-Xss1280k to the Linux build. I am not sure if that is still needed and if it might be related to the reports that on Linux some users have experienced very high RAM consumption.
@chimp1984 chimp1984 changed the title Investigate if -BjvmOptions=-Xss1280k for linux build is needed Investigate if -BjvmOptions for linux build is still needed Nov 24, 2019
@chimp1984 chimp1984 mentioned this issue Nov 25, 2019
Closed
@HiDef888
Copy link

Hello Chimp,
I am one of the users having RAM consumption issues starting Bisq. I commented out the line in Bisq.cfg -Xss1280k you refer to, to see if it affected my RAM usage, and it did not fix the issue unfortunately. I have also tried to force limiting the JVM to certain constraints and that doesn't work for me either.
Thanks

@ripcurlx ripcurlx mentioned this issue Feb 6, 2020
Closed
@ripcurlx ripcurlx added the is:priority PR or issue marked with this label is up for compensation label Feb 18, 2020
@ripcurlx ripcurlx added this to To do in Critical Bugs Board via automation Feb 18, 2020
This was referenced Feb 18, 2020
Closed
Closed
Closed
Closed
Closed
Closed
Closed
@ripcurlx
Copy link
Contributor

Related to: #3128, #3657, #3918, #3917, #3787, #3786, #3686, #3677, #3343

@ripcurlx ripcurlx mentioned this issue Feb 18, 2020
Closed
@ripcurlx ripcurlx added the is:critical https://bisq.wiki/Critical_bug label Feb 18, 2020
@cbeams cbeams added the a:bug label Feb 27, 2020
@freimair
Copy link
Member

maybe we should try adding a -XX:MaxRAM=2147483648 to the java opts of the bisq-desktop binaries. @ghubstan had some success with that and I can confirm that this limits the RAM usage drastically even after days of always-on.

@freimair freimair mentioned this issue Mar 11, 2020
Merged
@ghubstan ghubstan mentioned this issue Mar 13, 2020
Merged
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
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
@cd2357
Copy link
Contributor

cd2357 commented May 9, 2021

I am one of the users having RAM consumption issues starting Bisq. I commented out the line in Bisq.cfg -Xss1280k you refer to, to see if it affected my RAM usage, and it did not fix the issue unfortunately. I have also tried to force limiting the JVM to certain constraints and that doesn't work for me either.

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
Critical Bugs Board automation moved this from To do to Done May 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
a:bug is:critical https://bisq.wiki/Critical_bug is:priority PR or issue marked with this label is up for compensation on:Linux
Projects
Critical Bugs Board
  
Done
Milestone
No milestone
Development

No branches or pull requests
6 participants
@ripcurlx @cbeams @freimair @cd2357 @HiDef888 @chimp1984