Major I/O write bytes on the Spotify Desktop app. It will kill SSD drives in record time (fixed)

**********************************************************
EDIT: According to Spotify this issue has been fixed in the 1.0.42 version so the case has been closed. Personally I have no more issues with this anymore on any computer. Thanks everyone for making this happen !!!

**********************************************************

original post:
Major disk write activity detected on the Windows/Mac app. Does not behave like that when using the browser player.

Please look into this thread, more details there:
https://community.spotify.com/t5/Desktop-Linux-Windows-Web-Player/Spotify-killing-my-SSD/m-p/1365378

 

Attached readouts from a Win7/64 PC during one hour and ten minutes. No offline playlist syncs and zero songs were played during that hour, only the spotify app tray active in background!

No disk drive, SSD or standard HDD can take that rate for a long period of time.

 

PLEASE ADDRESS THIS ISSUE ASAP OR BE THE NEXT SAMSUNG NOTE !!!

 

temp.jpg
Thank you for bringing this issue to our attention. As some of you have noted, the prior version of the Spotify desktop client may sometimes have caused unnecessary data to be written to storage devices. This issue has been fixed in the current version of the desktop client (1.0.42), released November 11th, and rolled out to all our users. If you try to run an older version, you will see it automatically restart and update to the new version shortly after you log in.
 
If for some reason you should encounter problems with the auto update, just follow these steps to perform a full reinstall.
 

If you're running a deprecated OS (Windows XP, Vista; OS X 10.7, 10.8), don't worry. A fix has automatically been rolled out to you too. To ensure you're running this version, just close/reopen the desktop app twice.

 
Again, we greatly appreciate your help here, and hope that you will continue to flag issues for us when they arise.

Related Issues

Comments
Casual Listener

I can't agree ; browsers may well be part of the equation, but mercury.db is clearly directly used by Spotify - the string "mercury" even occurs in the main executable.

 

The common theme may well be poor handling of SQLite DBs as a cache for frequently updated value pools, but Spotify is clearly doing something specific to cacheing music metadata with this DB.

Casual Listener

Hey guys, i got an idea, that worked on my laptop (windows 10 here, but works down to windows 7. There should be some alternative for mac).

Anyone having more than 8gigs of ram ? I have 16, so I created a 4gb ram disk, and used windows's mklink command to make a symbolic link from C:\Users\<you>\AppData\Local\Spotify to the ramdisk. therefore, all writes to this folder (including mercury.db) are redirected to the ramdisk. And spotify just doesn't see the change, so it works flawlessly.

 

I checked, deleting this folder doesn't log you out, and spotify still works. As the ramdisk is cleared after a restart, you'll always get a new fresh DB, and all the writes redirected to the ramdisk. So now your SSD is safe from it 😄 


Spotify's important files (the actual app and some other stuff are in C:\Users\<you>\AppData\Roaming\Spotify. Don't move that to the ramdisk. Your preferences are also in this folder, that's why you're not logged out.

For the ramdisk, i use ImDisk, with it's UI. Configure it to also redirect your temp while you're at it 🙂 The good part, it's dynamic, if you give it 4gb, it won't use 4gb of ram, but just the space needed for what's inside, with an upper limit of 4gb (configurable).

 

Edit : for more info and detailed guide : http://blog.scaleprocess.net/spotify-heavy-io-problem/

hope it helps. If you have any questions, just ask 🙂

PS: This is temporary safe fix, but we still wait a REAL patch. 

Casual Listener

Hey guys, i got an idea, that worked on my laptop (windows 10 here, but works down to windows 7. There should be some alternative for mac).

Anyone having more than 8gigs of ram ? I have 16, so I created a 4gb ram disk, and used windows's mklink command to make a symbolic link from C:\Users\<you>\AppData\Local\Spotify to the ramdisk. therefore, all writes to this folder (including mercury.db) are redirected to the ramdisk. And spotify just doesn't see the change, so it works flawlessly.

 

I checked, deleting this folder doesn't log you out, and spotify still works. As the ramdisk is cleared after a restart, you'll always get a new fresh DB, and all the writes redirected to the ramdisk. So now your SSD is safe from it 😄 


Spotify's important files (the actual app and some other stuff are in C:\Users\<you>\AppData\Roaming\Spotify. Don't move that to the ramdisk. Your preferences are also in this folder, that's why you're not logged out.

For the ramdisk, i use ImDisk, with it's UI. Configure it to also redirect your temp while you're at it 🙂 The good part, it's dynamic, if you give it 4gb, it won't use 4gb of ram, but just the space needed for what's inside, with an upper limit of 4gb (configurable).

hope it helps. If you have any questions, just ask 🙂

PS: This is temporary safe fix, but we still wait a REAL patch. 

Newbie

I have to report the same issue. Over 150 GB has been written on my disk today. This kinda sucks, knowing how it's affecting my SSD. I don't really want to leave Spotify and start using Apple Music. Please, fix it! 🙂

Casual Listener

@PavelHru , please have a look at the last answer on page 9, and tell me if it solves the problem. This solved it for me 🙂

Newbie

in settings you can change cache location

but check frequently because spotify is stupid and change it again in the ssd!

 

 

Casual Listener

yes but this doesn't move the mecury.db, which the culprit.

Please have a look at the previous page (9, last post), i wrote an answer with a possible solution, which is using a ramdisk and symlinks (yes, on windows).

Newbie

I also have this issue. macOS 10.12.1, 15" Mid-2014 Macbook Pro. Screesnhot attached. Sort this out Spotify.Screen Shot 2016-11-07 at 00.00.46.png

Newbie

This scares me a lot 😕

 

Screen Shot 2016-11-07 at 15.10.35.png
Newbie

37.7 GB, what?!?! At least clean up some of that, goddam.