Need help? Check out Spotify Answers for solutions to a wide range of topics.
Windows 10 1803, GTX 980 430.86, FX4100
I uninstalled and reinstalled both desktop and app several times
My Question or Issue
A few days ago, Spotify decided to start locking my CPU at 100%. When I attempt to exit, only one of the four Spotify processes goes away and the CPU hog continues. When I attempt to forcefully terminate, one process stays behind but at 50% CPU, will not terminate with a "attempt to access exiting process" error. When left alone for a few hours, process eventually used ALL 32GB of my RAM.
All of this happened after one, or all, of the following activities: toggling hardware acceleration, deleting "Liked from Radio" playlist, changing proxy setting to "No Proxy". If it's related, I also noticed Spotify had trouble downloading some of my playlist thumbnails a few days earlier. My Muse playlist, created by Warner Music, never could download (could be deleted) as well as my top songs 2016 lost its custom thumbnail. Exiting Spotify or clicking "restart Spotify" after either option above ends up with the same problem. Uninstalling, reinstalling, uninstalling again, restarting computer, reinstalling again, uninstalling again, restarting computer again, and installing the Windows App version all end up with this problem. I have even tried updating drivers, especially audio drivers, to no avail.
So far, the only way I've been reliably able to exit Spotify is to suspend all the Spotify processes then terminate the one that had the heavy CPU usage. Interestingly, terminating the others then terminating the heavy one "unsuspends" it, causing heavy CPU usage again.
I also note that if I try to logout in the client, the window goes blank with the Spotify animated waiting symbol in the middle and it stays like that indefinitely.
Also, the robot check is ridiculous. I had to go through several "screens" and attempt the verification about a dozen times before it let me post. Each time I ended with a green checkmark and each time the "verification failed" error came back.