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

hbbr using unexpected amount of memory and error out after a day in self-hosted setup #438

Open
linhz0hz opened this issue Jul 5, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@linhz0hz
Copy link

linhz0hz commented Jul 5, 2024

Describe the bug
When I use the self hosted server, it works for a day but the server would consistently fail after some time (1-2 days). When looking into it I found the following.

Jun 28 20:34:19 ip-172-31-0-49 hbbr[422]: memory allocation of 488135971 bytes failed
Jun 28 20:34:19 ip-172-31-0-49 systemd[1]: rustdesk-hbbr.service: Main process exited, code=killed, status=6/ABRT
Jun 28 20:34:19 ip-172-31-0-49 systemd[1]: rustdesk-hbbr.service: Failed with result 'signal'.
Jun 28 20:34:19 ip-172-31-0-49 systemd[1]: rustdesk-hbbr.service: Consumed 8.722s CPU time.

The server works after a restart.

Describe the environment
Installed on AWS EC2 instantce. Since rustdesk is quite lightweight, I used t3.nano instance with only 0.5GB of memory allocated. During normal operation this seems to be perfectly sufficient, but occationally I get the above error message, it seems hbbr is asking for a lot of memory sometimes.

Is this expected behabior? Also this is quite similar to issue #96 which was not fully explained.

@linhz0hz linhz0hz added the bug Something isn't working label Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant