gnome-music uses too much processing power
Description of the problem:
gnome-music use way too much CPU processing power for a music player, in the screenshots below you can see that it's using ≈ 54% of the CPU processing power, it's almost always in the top of the list of the apps when sorting by CPU usage. vlc for example --which is a video player-- use way less processing power, it max at 8% of CPU usage, whilst gnome-music sometimes use more than 80% of the CPU
Report:
this is happening in chronological order, all the % values refer to CPU usage, and the app is set to "Shuffle/Repeat Off":
- launching gnome-music without playing any song: CPU usage stay between 0% and 2%
- playing a random song: CPU usage still between 0% and 2%
- randomly jumping to different parts of the song: CPU usage still between 0% and 2%
- clicking 'next': CPU usage jump to 18% then stay between 11% and 14% (maybe if i was to wait more it will get down to 1%?)
- randomly jumping to different parts of the song: CPU usage jump to 24% then slowly get down to 1% and stay there (even tho i am still randomly jumping to different parts of the song)
- clicking 'next' many time: jump to 60%, then slowly decline back to 1%
- after i stopped reporting my actions, and started using the app as i would usually do, playing some of my favorite songs, and navigating through some playlists, etc..: the app seem to stay at ≈ 40%
- i decide to click 'next' many times, and jump from a song to another: it jump to ≈ 60% then it stay mostly between 66% and ≈50%, sometimes it get down to 20% or 30%, but mostly it stay between 66% and ≈50% as i said
- after writing this, and before posting this bug, i checked it's usage, it seem to mostly stay 40%
Steps to reproduce
i have no idea, i just usually keep it running in a different workspace while i am working, i notice that my laptop get slower and less responsive, when i check the system monitor the problem is almost always gnome-music using too much %CPU
Environment:
- OS: Arch Linux
- Gnome Music: v3.38.2
Screenshots:
Random guesses and observations:
it seem to me like --ignoring the spikes-- there's a baseline, that seem to easily increase (changing songs for example) the baseline seem to take too long to decrease, longer than the length of a song
could it be the shuffling? or maybe it have to do with the songs names (written in arabic and english)? does it have to do with the fact that the app is written in python?