Describe the bug
Spotatui experiences 100% CPU usage triggered by switching playback devices or after long periods of inactivity. Specifically, when transferring playback from Spotatui to a mobile device, the program becomes "dominant" to device changes (forcing playback back to itself) and also keeps maximum CPU load until the process is manually terminated.
To Reproduce
- Launch Spotatui and start playback.
- Switch the playback device from Spotatui to a phone (via Spotify Connect).
- Observe that Spotatui immediately attempts to regain control as the active playback device.
- Try to switch back to the phone from the mobile app (the toggle fails unless changed directly within Spotatui).
- Check system resources to confirm 100% CPU usage.
Alternative: Leave Spotatui idle without playback for several hours and monitor CPU spikes.
Expected behavior
- The handoff between devices should be seamless without CPU spikes.
- Spotatui should remain idle/backgrounded when another device is selected as the primary output.
- CPU usage should remain minimal when the application is not actively playing audio or syncing large amounts of data.
Desktop (please complete the following information):
- Trisquel GNU/Linux
- Bash running inside two nested Screen sessions
- v0.38.0
Describe the bug
Spotatui experiences 100% CPU usage triggered by switching playback devices or after long periods of inactivity. Specifically, when transferring playback from Spotatui to a mobile device, the program becomes "dominant" to device changes (forcing playback back to itself) and also keeps maximum CPU load until the process is manually terminated.
To Reproduce
Alternative: Leave Spotatui idle without playback for several hours and monitor CPU spikes.
Expected behavior
Desktop (please complete the following information):