4 ms·

Wow. I've got Apple Music/iTunes running for a week or so on this Catalina macOS and the process viewer reports 300MB (including sub-processes). I assume it's a

Wow. I've got Apple Music/iTunes running for a week or so on this Catalina macOS and the process viewer reports 300MB (including sub-processes). I assume it's a native application. How does Spotify manage to use so much RAM??

kitsunesoba 7y ago
The Spotify desktop client is architected such that each pane in the main window is essentially its own separate webapp, complete with duplicate (and triplicate, quadruplicate, etc) dependencies. They did this so their various teams don’t have to talk to each other. Desktop Spotify has been a resource hungry mess for years now. It used to be known for prematurely wearing out SSDs by constantly writing stuff (cache I think?) to disk.
- csnover 7y ago
  > It used to be known for prematurely wearing out SSDs by constantly writing stuff (cache I think?) to disk. They were constantly vacuuming some SQLite database.[0] [0] https://arstechnica.com/information-technology/2016/11/for-five-months-spotify-has-badly-abused-users-storage-drives/ https://arstechnica.com/information-technology/2016/11/for-f...
  - felubra 7y ago
    Does anybody know if this was fixed?
    - montag 7y ago
      Yes, it was.
- atombender 7y ago
  They also have this problem where a "Spotify Helper" can crash constantly, and you won't notice it unless you look at the process tree. On macOS, this will start a ReportCrash process, and end up taking up an entire CPU core just repeatedly crashing, reporting a crash, restarting, etc. It also significantly impacts battery life. This happens every day for me. It's arguably worse than the SSD-killing SQLite vacuum problem they had.
  - derefr 7y ago
    I haven't seen this one personally, but I get the same crash-loop from the Discord app. Weirdly enough, the crashes don't seem to affect any of the app's functionality.
- ajxs 7y ago
  > They did this so their various teams don’t have to talk to each other. This is absolutely dreadful. I've unfortunately worked in multiple organisations where teams deconstructed their web-based products into microservices for this very reason.
- city41 7y ago
  I have found it to be rather buggy. I sometimes can't get songs to play, and other times can't get them to pause :) I switched to using their web interface in Firefox which has been totally rock solid.
- fmakunbound 7y ago
  > They did this so their various teams don’t have to talk to each other. This is just insane.

kitsunesoba 7y ago

The Spotify desktop client is architected such that each pane in the main window is essentially its own separate webapp, complete with duplicate (and triplicate, quadruplicate, etc) dependencies. They did this so their various teams don’t have to talk to each other. Desktop Spotify has been a resource hungry mess for years now. It used to be known for prematurely wearing out SSDs by constantly writing stuff (cache I think?) to disk.

csnover 7y ago
> It used to be known for prematurely wearing out SSDs by constantly writing stuff (cache I think?) to disk. They were constantly vacuuming some SQLite database.[0] [0] https://arstechnica.com/information-technology/2016/11/for-five-months-spotify-has-badly-abused-users-storage-drives/ https://arstechnica.com/information-technology/2016/11/for-f...
- felubra 7y ago
  Does anybody know if this was fixed?
  - montag 7y ago
    Yes, it was.
atombender 7y ago
They also have this problem where a "Spotify Helper" can crash constantly, and you won't notice it unless you look at the process tree. On macOS, this will start a ReportCrash process, and end up taking up an entire CPU core just repeatedly crashing, reporting a crash, restarting, etc. It also significantly impacts battery life. This happens every day for me. It's arguably worse than the SSD-killing SQLite vacuum problem they had.
- derefr 7y ago
  I haven't seen this one personally, but I get the same crash-loop from the Discord app. Weirdly enough, the crashes don't seem to affect any of the app's functionality.
ajxs 7y ago
> They did this so their various teams don’t have to talk to each other. This is absolutely dreadful. I've unfortunately worked in multiple organisations where teams deconstructed their web-based products into microservices for this very reason.
city41 7y ago
I have found it to be rather buggy. I sometimes can't get songs to play, and other times can't get them to pause :) I switched to using their web interface in Firefox which has been totally rock solid.
fmakunbound 7y ago
> They did this so their various teams don’t have to talk to each other. This is just insane.