Skip to main content
Contributor I
February 7, 2019

Sonos Mac APP Memory Usage

  • February 7, 2019
  • 22 replies
  • 1256 views
Does it make sense Sonos APP for Mac to be taking so much memory (~2GB) , or I am the only one having the issue with it ?

Analysis of sampling Sonos (pid 4600) every 1 millisecond
Process: Sonos [4600]
Path: /Applications/Sonos.app/Contents/MacOS/Sonos
Load Address: 0x100b2b000
Identifier: com.sonos.macController
Version: 10.0 (48.2.61220)
Code Type: X86-64
Parent Process: ??? [1]

Date/Time: 2019-02-07 12:10:18.701 +0100
Launch Time: 2019-02-05 21:38:41.527 +0100
OS Version: Mac OS X 10.14.2 (18C54)
Report Version: 7
Analysis Tool: /usr/bin/sample

Physical footprint: 1.9G
Physical footprint (peak): 2.0G
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.

22 replies

Edward R
Retired Sonos Staff
February 14, 2019
Hi, ilija_g. I'll be very honest in saying I'm not sure why that is happening. Do you have a music library that you use in conjunction with Sonos?
Try searching our articles for help with your question: https://www.sonos.com/en/support
ilija_gAuthor
Contributor I
February 14, 2019
Hi Edward R, I don't have any local music library (neither on my network) associated with Sonos app.
I am simply using Sonos app with Spotify service. But I have noticed one more thing, that the app takes more and more memory with time, and it seems like a memory leakage to me.
Check below:

Sampling process 92959 for 3 seconds with 1 millisecond of run time between samples
Sampling completed, processing symbols...
Analysis of sampling Sonos (pid 92959) every 1 millisecond
Process: Sonos [92959]
Path: /Applications/Sonos.app/Contents/MacOS/Sonos
Load Address: 0x104b15000
Identifier: com.sonos.macController
Version: 10.0 (48.2.61220)
Code Type: X86-64
Parent Process: ??? [1]

Date/Time: 2019-02-14 13:07:56.584 +0100
Launch Time: 2019-02-14 13:04:24.517 +0100
OS Version: Mac OS X 10.14.2 (18C54)
Report Version: 7
Analysis Tool: /usr/bin/sample

Physical footprint: 188.3M
Physical footprint (peak): 269.3M
pwt
Virtuoso
February 14, 2019
As a comparison, here's my Sonos process dump:

Analysis of sampling Sonos (pid 2412) every 1 millisecond
Process: Sonos [2412]
Path: /Applications/Sonos.app/Contents/MacOS/Sonos
Load Address: 0x1045b5000
Identifier: com.sonos.macController
Version: 10.0 (48.2.61220)
Code Type: X86-64
Parent Process: ??? [1]

Date/Time: 2019-02-14 12:07:43.273 +0000
Launch Time: 2019-02-12 09:58:41.495 +0000
OS Version: Mac OS X 10.14.3 (18D109)
Report Version: 7
Analysis Tool: /usr/bin/sample

Physical footprint: 242.8M
Physical footprint (peak): 246.4M
4 x P:5 | Sub | 4 x P:1 | 3 x Connect | 2 x Boost | Connect:Amp | 2 x One | Amp | Move | Port | Era 300
pwt
Virtuoso
February 14, 2019
But I have noticed one more thing, that the app takes more and more memory with time, and it seems like a memory leakage to me.
A memory leak is plausible. Worth investigation by Sonos. Having said that it's no big deal to restart the controller, since it's essentially stateless and the restart doesn't interrupt playback.
4 x P:5 | Sub | 4 x P:1 | 3 x Connect | 2 x Boost | Connect:Amp | 2 x One | Amp | Move | Port | Era 300
ilija_gAuthor
Contributor I
February 14, 2019
pwt,
Absolutely no critical issue here. 🙂.

But it is a problem when I am working and need every byte of memory and my computer becomes slow, and the reason for this is Sonos APP which (by my opinion) should be just a helper APP.

Don't get me wrong I am not hating here 🙂 . Sonos guys are doing great job.
pwt
Virtuoso
February 14, 2019
pwt,
Absolutely no critical issue here. 🙂.
But it is a problem when I am working and need every byte of memory and my computer becomes slow, and the reason for this is Sonos APP which (by my opinion) should be just a helper APP.
Don't get me wrong I am not hating here 🙂 . Sonos guys are doing great job.

No, I didn't read it as 'hate' thread at all 🙂 I think it's a defect worth reporting. There are plenty of dev tools available to detect memory leaks. It's also possible that the app is doing a lot of cacheing (images, etc.) without limiting the cache size.
4 x P:5 | Sub | 4 x P:1 | 3 x Connect | 2 x Boost | Connect:Amp | 2 x One | Amp | Move | Port | Era 300
Edward R
Retired Sonos Staff
February 14, 2019
Given what has been identified here, I think it may be worth getting in touch with us by telephone. It seems necessary that we log into your computer to run some tests remotely. Thanks for your patience in this matter, I'm sure it will be resolved fairly quickly once you're in touch with the appropriate team.
Try searching our articles for help with your question: https://www.sonos.com/en/support
ilija_gAuthor
Contributor I
February 14, 2019
Don't get me wrong but I do not have enough time to search for a contact and get in touch by phone 🙂. I will continue restarting the app until they figure the issue eventually and sort it out, or have any other means of communication.
Edward R
Retired Sonos Staff
February 14, 2019
That's a pity, although I do understand. Unfortunately it does seem that it would require a more hands-on approach, as there will likely be some level of data gathering involved. I'm not sure if it is an isolated event to your computer, though if it persists beyond, say, the next update, we may need to get you some real-time support. Until then, let us know if you have any further questions.
Try searching our articles for help with your question: https://www.sonos.com/en/support
ilija_gAuthor
Contributor I
February 14, 2019
Thanks your effort Edward, I do appreciate it.
Anyway, I will try to reproduce the problem myself and send you some more information when (and if) it happens again.