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.

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

Java Heap Error #5368

Closed
paulmercier-bisq opened this issue Mar 28, 2021 · 3 comments
Closed

Java Heap Error #5368

paulmercier-bisq opened this issue Mar 28, 2021 · 3 comments

Comments

@paulmercier-bisq
Copy link

Description

Bisq seems to crash

Version

Version 1.6.0.

Steps to reproduce

Seems to happen after leaving Bisq open with computer hibernating, unsure tho.

Expected behaviour

Bisq should work smoothly.

Actual behaviour

Bisq crashes.

Screenshots

heap

Device or machine

Ubuntu 20.04.2 LTS, Gnome 3.36.8, X11.

Additional info

Last 1,000 lines of bisq.log :
1000.log

@boring-cyborg
Copy link

boring-cyborg bot commented Mar 28, 2021

Thanks for opening your first issue here!

Be sure to follow the issue template. Your issue will be reviewed by a maintainer and labeled for further action.

@wallclockbuilder
Copy link
Contributor

Is it permanently broken?
Is your hard drive SSD or HDD?
Have you tried a system restart?
Share the last page of your log file if it breaks again after doing a post-restart run.

@cd2357
Copy link
Contributor

cd2357 commented Mar 28, 2021

Seems to happen after leaving Bisq open with computer hibernating, unsure tho.

Generally its not a good idea to hibernate the computer while Bisq is running. For it to work properly, it needs to maintain several tor connections open and constantly listen for network and trade updates, among other things. Hibernation/sleep interrupts and prevents this.

If you do plan to hibernate/sleep the PC, best to first close Bisq. If you have open trades or other reasons why you'd like to keep Bisq running, then ideally you'll disable hibernation in the OS settings.

If it still happens even when not hibernating/sleeping, let us know, I'll reopen the issue.

@cd2357 cd2357 closed this as completed Mar 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants