Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

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

Submitted by on ‎2016-10-21 07:16 AM
Status: Closed

**********************************************************
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.
See more ideas labeled with:
Comments
m2vihand
Newbie
‎2016-11-15 07:01 AM

Hi everybody,

can anybody tell me if this major drive write issue is present if I use hdd only, not ssd? Thanks.

0 Likes
SaSa83
Newbie
‎2016-11-15 08:00 AM
Sure it is. Even a hard drive has a limited lifetime and amount of data it
can write / read before failing. Although it will not fail as fast as a SSD.

But the issue seems to be fixed in the latest version.
0 Likes
IsaLRMA
Newbie
‎2016-11-15 08:58 AM

How can I Check and clean what spotify left on my mac? can anyone help me out?
thanks people 🙂

0 Likes
tebruno99
Newbie
‎2016-11-15 04:40 PM
@enigmaxg2
TRIM doesn't auto balance across flash cells so the same ones don't get hit all the time.  SSD auto balancing is built into the firmware, you cannot prevent it from happening. Sometimes auto balancing decides that a block that has data hasn't been written to in a long time so the balancing will decide to move that block to a new place and write the new data to that block.  All TRIM does is let the auto balancing know, "Hey you don't have to move that one to a new place because it is not actually in use".  So TRIM does reduce writes but not to very much effect, it is mostly a performance tool.
 
Auto defrag is also a pretty minor issue. Defragging a disk doesn't read and write every block, the effects are pretty mild over the live of the computer.
 
So you are right, there is an effect. However Windows XP isn't nearly about to 'wear out the drive'. The drive is more likely to die due to physical failure.
0 Likes
Daniman
Newbie
‎2016-11-15 06:13 PM
Thanks a lot for the explanation. This is what I thought. The trim feature
was a performance tool and not a necessity to avoid that the unit dies... I
was reading about it before buying the unit for a windows xp system...

I use SSD tweaker and have updated the firmware to the last version...

And the question again. Somebody knows about the Spotify app (windows
xp)... The last version is the 1.0.20. Is this version affected ?? (SSD
killer?)

Thanks!!
0 Likes
user-removed
Not applicable
‎2016-11-16 02:27 AM

I have the newest update 1.0.42 as described and it does not fix the problem.  Ran for a few minutes and saw 250MB of writes.  Easily still having huge problems with drive activity here.

0 Likes
carrerr
Music Fan
‎2016-11-16 05:57 AM

@user-removedAnd does that write rate continue beyond the first few minutes? There are multiple reports of the bug having been fixed, so I'd say anyone claiming the opposite needs to post actual monitoring data for a time period of at least 30 minutes if they want this to go anywhere. As explained earlier, it's perfectly normal for the client to write quite a bit of data moments after launch: the mercury.db rewrite still occurs, just not all the time; in addition, cache writes always accompany streaming use.

 

0 Likes
jor3ka
Regular
‎2016-11-16 07:27 AM

gozargozarian  try a fresh install or try delete your spotify data folder and let spotify recreate.

del /f /s /q %LocalAppData%\Spotify

 

It's fixed in 1.0.4.2 but I'm not fond of the new design. It's actualy faster than earlier versions though.

0 Likes
marcelklacan
Newbie
‎2016-11-16 07:44 AM

Please somebody tell us when spotify will repair this issue. I'm waiting for it and then i will come back.

0 Likes
xjapan666
Newbie
‎2016-11-16 09:53 AM

If Spotify can't fix this problem immediately, I will stop to pay for this service which is killing my SSD. No one likes to pay money and let his PC to be a P2P server.

0 Likes

Related Issues