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:


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.




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.
Casual Listener

OS is macOS Sierra 10.12.1 and my Spotify Client version is Reinstalling had no affect. Spotify wrote over 1GB for 3 songs. 


@samthorne wrote:


You can solve the problem on OSX in the following way:

Open /Applications/ in a hexeditor.

Search for "VACUUM;" Replace with "xxxxxx;"


Used the above solution and Spotify has signficantly reduced writes. Spotif wrote 60MB for 6 songs listened whereas before it was 1GB+ for 3 songs (which means over 2GB for 6 songs).

Thanks to the OP for the solution, hopefully a official update comes from Spotify.


I'm sorry for leaving the thread with such a clickbait title for such a long time, I forgot about the thread since I stopped using spotify (partially because of this issue)


Anyways I've changed the title to be more descriptive of the problem.


I'm using Mac OS X El Capitan,


Just checked the Activity Monitor on Disk tab, I noticed spotify has written 6.36 GB of data! I haven't played any song, I kept spotify open since startup.

Screen Shot 2016-11-09 at 4.44.37 PM.png

There´s no answer from Spotify? Nothing at all?

 Apple´s music it´s loving this, i´m sure...


@zigityzigity_ wrote:

Excited to hear this is temporarily bypassing our issue. Would someone kindly report back with your results after a day of usage post-"VACUUM;" for the greater good?

After 16 or so hours it's looking great. Spotify has written just 17.6 MB. Without the vacuum fix that would normally be about 30 GB on my machine, two thousand times more.


Still waiting for Spotify to say or do something about this debacle.

Casual Listener

I looking at my Spotify App and I have not subscription because of missing equalizer but I notice that when advert starts playing, Spotify.exe starts writing to disk "something" with 50-60 MB/s speed in several seconds. Whaaat. 


Same here, the hex-editing solution worked greatly.
I've pinged the Spotify Engineering team on Twitter to let them know someone here found a solution... Let's hope they'll take this issue in consideration


Is there an equivalent fix on Windows?

Casual Listener

Same fix : the change is editing a SQL script embedded in the program file. It's the same underlying DB technology on all three platforms, so the same fix should apply, unless the Windows version has some kind of checksumming technology that prevents it running if you edit it.


Unfortunately I couldn't find "VACUUM;" in the file "



Related Issues