Skip to main content
Answer

The macOS desktop app is taking huge amount of RAM

  • February 19, 2025
  • 3 replies
  • 107 views

The app uses 1.15 GB or RAM. I’m not even using it actively. It’s huge!

For the support, my diagnostic number is **********.

Related:

Moderator edit: Recorded and removed diagnostic number

 

Best answer by Corry P

Hi ​@koala44 

Welcome to the Sonos Community!

Sorry to hear of this issue you are having with the Sonos app taking up system memory.

Please close the Sonos app and reopen it to free up memory.

We are aware of this issue, but as the Desktop Apps will soon be depreciated in favour of the Web App, work will not be done to resolve it.

If it continues to cause problems for you, I recommend that you close the app when it’s not in use, or use the Web App instead, linked to above.

I hope this helps.

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

3 replies

Corry P
Forum|alt.badge.img+19
  • Sonos Staff
  • Answer
  • February 20, 2025

Hi ​@koala44 

Welcome to the Sonos Community!

Sorry to hear of this issue you are having with the Sonos app taking up system memory.

Please close the Sonos app and reopen it to free up memory.

We are aware of this issue, but as the Desktop Apps will soon be depreciated in favour of the Web App, work will not be done to resolve it.

If it continues to cause problems for you, I recommend that you close the app when it’s not in use, or use the Web App instead, linked to above.

I hope this helps.


  • February 20, 2025

We are aware of this issue, but as the Desktop Apps will soon be depreciated in favour of the Web App, work will not be done to resolve it.

PMFJI, but does the deprecation of the PC program only affect the S2 system, or does it affect the S1 system as well?


Corry P
Forum|alt.badge.img+19
  • Sonos Staff
  • February 20, 2025

Hi ​@amun 

Good point! Or is it a good question?

Web App is only available for S2 systems. So, if the S1 macOS app was using up system memory in this manner, I see how that would be something we should be addressing. As far as I am aware, however, this issue has not been reported with the S1 macOS app, only with the S2 app.

I hope this helps.