topic Re: Memory leak in Windows 10 client when using Local Files in Desktop (Windows)

Memory leak in Windows 10 client when using Local Files

ebol — Wed, 20 Jun 2018 04:51:00 GMT

I have a library of 10,000+ MP3s, and Spotify fails to index it. When I add the folder with my music, Spotify slowly starts using more and more memory and slows to a crawl, making it completely unusable until I kill the process in Task Manager. Once I do that, I can restart the client, and the folder is already gone from my Preferences page, so it doesn't attempt to start indexing it again automatically unless I re-add it.

Someone in my previous thread recommended adding the folders one at a time, but that is not option, as there are thousands of folders. Other meda players like Foobar and Media Monkey can index my music library without issue.

Spotify version 1.0.83.318.g6c07039d

Windows 10 Pro x64, build 17134

Re: Memory leak in Windows 10 client when using Local Files

Sebasty — Wed, 20 Jun 2018 15:34:17 GMT

Hey @ebol

Sorry to hear you're having issues with adding your files to Spotify!

10 thousand files is a whole lot of data though. I also recommend splitting it up in smaller bulks. You don't have to add one folder at a time, instead try splitting them into groups Spotify can manage to index.

Foobar is a very lightweight program and as far as I know it doesn't create files for mapping or storing information about your library. It just monitors the folders you've allowed it to monitor (and index).

Spotify and, for example, Windows Media Player both create special files, Spotify creates local_files.bnk file, WMP creates CurrentDatabase_372.wmdb for storing information in it. It might become very slow or even crash when you have particularly large library or when your computer in general is a little slow.

Let me know how you get on 🙂

Re: Memory leak in Windows 10 client when using Local Files

ebol — Wed, 20 Jun 2018 15:43:34 GMT

Foobar2000 also stores library data in a file.

There is obviously an issue in Spotify, as trying to index a large number of files causes tons of memory to be allocated until the program stalls out. This doesn't happen in any other popular media player.

I'm not interested in splitting up my library arbitrarily into many folders, I am just reporting a bug. I will continue using other programs to play my local media if it does not work in Spotify.