I have many of those programs you listed and none of them even approach Spotify in disk writes. This is the list I personally gathered which use LIBCEF, this doesn't mean all of them have this behavior, that will be proven or debunked until further testing is done (the confirmed ones are in bold), I think there a lot more apps and programs which do this. Or when possible, use alternative programs which don't rely on libcef.
#MUI THEMES SYMLINKER UPDATE#
The only solution for now is that Chrome devs become aware of the problem and push an update to both the browser and standalone engine then app developers integrate the new libcef ASAP. The problem extends even more when a huge list of software uses this library to render web content, so if you have one or more of these programs in your computer (and I'm sure you have), they add up and probably will reduce the drive lifespan a lot. Now it comes the part related to this thread, Spotify (among others) uses Libcef.dll to render web content, what's libcef? it's an embedded Chrome engine and as you probably guess, it has the same -uncorrectable for now- issue as the browser. But only Firefox has a way to mitigate the problem. Well, this is gonna be a giant text wall, but is a recommended reading if you want to keep a healthy SSD (and even HDD).įirst Firefox was discovered doing this: source, then I asked the guys there to do a test with other browsers, and as I expected, ALL of them are doing the same. The problem relies on the use of the Libcef (embedded Chrome engine) which Spotify uses (which also explains why it is so inefficient with it's resource usage on desktop) Major I/O write bytes on the Spotify Desktop app.
0 kommentar(er)
