-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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] Using 66% of a CPU when idle #969
Comments
This comment was marked as spam.
This comment was marked as spam.
Same problem here... I'm about to look for an alternative because my raspberry freezes and I have to restart it. |
I had the same problem, so I built a new docker image from master, and that sort of seems to have fixed it. |
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
Still relevant. @Lissy93, any chance you'll be able to look at this? If not, perhaps you have some hints as to how you'd diagnose it? |
Hey, This definitely doesn't sound good at all, weirdly I'm running a very similar setup (Pi 4, default Docker, etc) and no issues. |
@ohmantics, do you have an example config file to reproduce this issue? Also, does it still happen if you change the container command to run @Lissy93, is there any reason for the ARM-based Docker images to have |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
I also run Dashy with many other things on my Rpi 3B+ with 1GB RAM and Dashy is consuming very few MB and barely any CPU even when starting up. Can you confirm if you are running x64 or x32 ? |
This comment was marked as spam.
This comment was marked as spam.
This comment has been minimized.
This comment has been minimized.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as off-topic.
This comment was marked as off-topic.
In my case x64 |
Hi Keep in mind V3 has breaking changes: |
Not seeing the original issue now. It did take several re-pulls for the build to complete without errors; not sure why since it says "possible error, check logs" and there are no logs to see. |
Awesome! Then I think we can close this. If you have changed the bind mounts and the port those errors shouldn't appear, yeah. Did you wait about 3 minutes longer and refreshed the page, after the error appears? |
Environment
Self-Hosted (Docker)
System
Ubuntu 22.0.4
Version
2.1.1
Describe the problem
With no browser windows taking to dashy, the "node server" process is using 66% of a CPU core at minimum. Presumably this is background processing such as the docker healthcheck. There's no rebuild running. It's not going to zero at any point. With any browser window open, it goes up to 125% and stays there or above. However, this all seems very excessive for what's logically happening.
This was a straight-forward docker install using Portainer on a Raspberry Pi 4 running Ubuntu 22.04. This is enough CPU use to trigger the cooling fan on this box, hence why I've noticed it.
Additional info
partial output of pstree -a -p:
Please tick the boxes
The text was updated successfully, but these errors were encountered: