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

High memory usage, killed by OOM daemon #400

Open
nerdv2 opened this issue Dec 16, 2024 · 7 comments
Open

High memory usage, killed by OOM daemon #400

nerdv2 opened this issue Dec 16, 2024 · 7 comments

Comments

@nerdv2
Copy link

nerdv2 commented Dec 16, 2024

Hi, thank you for this project and I have been using it for almost a year now.

These past few months I keep encountering crashes and really sluggish performance and experience with the app due to excessive memory usage xpiped taken. Startup time could take around 1-2 minutes, using around 2-3GB of RAM and keep climbing until I close the application or killed by systemd-oomd.

I am using Git sync without encryption and currently have 12 groups and 384 connections.

Version: Community Edition 13.4.3
OS: Ubuntu 24.04 LTS

image

@crschnick
Copy link
Member

That must be a bug, anything over 1GB is too much. I have 500+ with git for testing and it doesn't even reach 1GB.

Can you try to create a heap dump with something like https://visualvm.github.io/download.html ?

@nerdv2
Copy link
Author

nerdv2 commented Dec 16, 2024

Thank you for the quick response @crschnick

What version of Java do I need to create a heap dump? It seems I can't click the button to create one.
And it seems the heap size is way bigger than it currently consumes, around 1GB, as you said.

Screenshot from 2024-12-16 16-11-33

@crschnick
Copy link
Member

Ehm can you use /opt/xpipe/app/scripts/xpiped_debug.sh to run it? If that also doesn't work, can you edit the debug script and remove the -XX:+DisableAttachMechanism option?

@crschnick
Copy link
Member

And if you succeed, you can upload the file somewhere and send it to me via email at [email protected]

@nerdv2
Copy link
Author

nerdv2 commented Dec 16, 2024

Unfortunately running the debug option still doesn't show the option in VisualVM, and there's no disable attach mechanism within the debug script.

image

@crschnick
Copy link
Member

So I will try to release the first XPipe 14 test build in a few days, and I will probably just build a heap dump functionality into it. I think it's best if I come back to you in a couple of days when this is ready

@crschnick
Copy link
Member

Can you try this: https://github.com/xpipe-io/xpipe-ptb

In the troubleshoot options, there is a heap dump button.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants