-
Notifications
You must be signed in to change notification settings - Fork 109
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
mopidy run in docker on armhf hangs with 100% CPU usage #402
Comments
Can you provide a log ? |
nothing important in mopidy logs.
|
also i'm watching cpu usage with htop. it shows that most of the usage is RED - Kernel threads |
And non-spotify tracks don't have this issue? Do they still have the alsa param errors? |
local files are working and produce such log
|
I can reproduce the issue with gst-launch command. First something that works (http stream):
and spotify that hangs with 100% CPU usage:
On the other armhf system, without docker:
This does not hang and fails with credentials issue as expected. |
and log with GST_DEBUG=5: after launching the command this is the part of log that keeps repeating endlessly:
|
I built gst-plugin-spotify v.0.13.2 in debug version. started with rust-gdb and this is what I get after starting gst-launch commad.
|
Do you have the same versions of Gstreamer in Docker and non-Docker armhf setups? Can you try the latest release at https://github.com/kingosticks/gst-plugins-rs-build/releases/tag/gst-plugin-spotify_0.14.0-alpha.1-1 ? I don't think there's anything we can do about this here other than try and work out which upstream to take this to. |
Yes, versions are the same. also tried v0.14.0 - same result. Actually on the other host spotify works also in docker so I suspect that this issue is somehow related to the machine rather than docker itself. Unfortunetly I cannot test without docker on this machine (CoreElec) |
I have a armhf armbian bullseye system with mopidy in docker. It was WORKING with gst-plugin-spotify v0.9.1.
After the issue described here happend I had to upgrade gst-plugin-spotify to v0.13.1. Now it is NOT WORKING. I can go to web interface, select spotify song to play and hit play, but after that mopidy process goes 100% CPU and nothing else happens. Anyone has the same issue ?
I created the minimal deockerfile (below):
Dockerfile:
mopidy.conf:
The text was updated successfully, but these errors were encountered: