I use Roon 2.47 (1510) on a Mac mini running Sonoma 14.7.1. It's a very simple setup, everything Roon and my music library (7000 tracks - some local files and some on Tidal) all run in the one box, with playback via headphones and a Dragonfly Cobalt. The Mac mini is an M2 Pro with 32GB RAM and 2TB SSD.
Roon appears to have a memory leak - on booting it will start and consume 800 -1000MB of RAM, and every day that its open, chew through an additional 1-2GB of RAM. After 10 days or so, Roon will have consumed most of the available RAM and crash the computer.
Only workaround is to boot the Mac regularly, something I would prefer not to need to do.
Describe your network setup
There is no network to speak of, Roon and music library all run in the one device. Network to router is via ethernet, but Roon exhibits the same behaviour whether the Mac mini is using ethernet or wifi.
Are you saying that combined Roon apps usage is running to ~12 GB?
Certainly, the image doesn’t reflect this. The kernel is currently using 2.4 GB, and active memory has the lion share, but much less than physical memory. Roon accounts for just under 3 GB.
In UNIX (macOS), allocated memory isn’t freed immediately, so it is quite normal to see the amount of active memory increase over time. This doesn’t signify a memory leak.
Nonetheless, I’m sure Roon support can check this by running diagnostics on your account.
Hi @Andrew_Friis,
Welcome to the Roon community. Thanks for reaching out to us to ask about this. The best way for us to begin troubleshooting this issue is to take a look at your Roon logs. Can you please use the directions found here and send over a set of logs to our File Uploader? Let us know what you named the file when you have uploaded it and we will begin troubleshooting.
I uploaded a file called: MacOS memory leak Andrew Friis.zip Most of the RAM expansions occurs Tuesday 11 Mar while playing music. I look forward to your findings.
Thanks for sending those log files over! Looking over the logs, it looks like your RoonServer is stable, using between 1.2-1.7GB of RAM (which is expected), but your Roon UI logs do show the memory growth.
Looking over the UI aspect specifically, I see that there are many “network changed”, usually ~20 minutes apart from each other, but sometimes even 5 or 10 minutes apart. Are there any network events scheduled to regularly run on the Mac?
Do you have multiple networking interfaces active on your Mac (and if you do, can you try to disable all but one as a test) or do you have any VPN clients running on the Mac?
The Mac runs with an ethernet connection and I have had wifi on also, to facilitate airdrop between my iphone and the Mac. There are no network events scheduled and no VPN. I cannot think of anything that is causing the mac to swap networks, unless it goes to sleep (which is does after 20 mins).
I rebooted the Mac with ethernet only, and after only a couple of hours play both with local tracks and tidal tracks, the Roon UI is at 9.81GB of RAM.
Have you experienced any crashes in the last five days? If so, we’d like to request you to upload a copy of the Apple Crash Report from Console to our log uploader at your convenience.
Diagnostics don’t indicate any abnormalities in physical/virtual memory consumption in RoonServer in the most recent logset, but we do see uncategorized (999) network failures with upstream requests and some generic library indexing errors.
Please let us know if your symptoms have changed - we’re eager to pin down the cause and, if necessary, implement a fix with development.
We can agree the RoonServer isnt the issue, the unmanaged memory growth is in the Roon UI.
As outlined earlier, the Roon UI consumes about 1GB when first opened and grows until it consumes all available RAM and the Mac becomes unresponsive. The workaround is to close and open Roon again, freeing the RAM. RAM is consumed while Roon is playing at around 1GB per hour, regardless of whether the Mac is connected to a network or not. With 32GB RAM onboard it will take some time to crash the machine. I will send you a logfile when that happens.
The memory growth we can see in diagnostics corresponds to two conditions:
spinning rendering - the acceleration of virtual/physical memory consumption in the logset shared previously occurred while the home page was open in the background
network failures affecting image caching. Roon itself is encountering network reset events that temporarily sever its visibility to the server. It also loses sight of coreaudio through the loopback. This isn’t necessarily causal or even related, but it indicates some network conditions are present that interfere with Roon.
The constant rendering shouldn’t be occurring and we’ve escalated to development. We haven’t reproduced this in-house yet on the same OS - is there a specific page, other than the home page, on which you tend to leave Roon running when you’re not using it?
We’ll follow up with more information as soon as possible. Thank you again.
