-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[BUG] Dashy Memory Leak #637
Comments
This comment was marked as resolved.
This comment was marked as resolved.
Not something I've ever seen reported before, but there was a similar ticket a few days ago, which makes me think it could somehow relate to the latest release of Dashy, but no idea how. First user was using Unraid I think, so presumed the issue was there. They didn't provide enough info to look into it any further, and I was never able to recreate. Btw, there's the video linked, just says "Video unavailable - This video is private" |
Actually this ticket is a duplicate of #631. Closing... But if you could provide more info, like the logs, then I can reopen + look into it further |
Fixed the video. It should be viewable now. I just let the container run until it shutdown and here are the logs:
|
Thanks, yeah that definitely doesn't look good... |
Sounds good! If you end up getting this resolved leave a comment here please! I'd love to switch back to Dashy as my dashboard. |
Linking: #647 Can now confirm another user with (I believe) the same issue. And also on Unraid. I believe the issue is with the Node Alpine base image used ( maybe similar to nodejs/node#29038). I'm going to install unraid in a VM and hopefully recreate it. Once again, sorry about this, I'll keep you in the loop |
I'm not sure if this might be related, but it seems that dashy starts in something similar to a development mode, it watches files for changes and it serves js files separately. I think it was caused by this PR when we switched from I would recommend using |
Such issues should not arise anymore. Can you confirm this issue still happens with the latest dashy V3 ? Keep in mind, V3 introduces breaking changes: |
I appreciate you guys fixing the issue! Unfortunately I've switched to another dashboard app since I commented so I'm unable to confirm. |
Thanks for the response. I just heard back from others and it seems all fixed, so if you ever want, check out V3 of dashy again, there were some really exciting updates: |
Environment
Self-Hosted (Docker)
Version
2.0.8
Describe the problem
My Dashy container has been shutting down automatically after a while. I finally had some time to look into what is going on and there is a memory leak.
The amount of ram that Dashy consumes is constantly slowly growing. I took a video of what it looks like (I also showed what my Dashy UI looks like, what my container settings look like, and that this is the only container that I have this issue with):
https://www.youtube.com/watch?v=qxQEoMy8nC8
At the start of the video the container has only been up for about 8 minutes but it's already started to take up more than 4.9GBs of memory. It keeps going up (as of typing this it's up to 8.3GB of memory).
You can see in this screenshot what my container settings for Dashy are (you'll see that it's all default settings):
https://i.imgur.com/hMv7UWX.png
(at the end of typing this post Dashy is now consuming 10.1GB of memory)
Additional info
No response
Please tick the boxes
The text was updated successfully, but these errors were encountered: