Roon 2.0, Build 1128, Mac Mini 2020 M1, 16GB RAM, 256GB SSD, MacOS 12.2.1
Networking Gear & Setup Details
recent Xfinity modem/router connected by ethernet
Connected Audio Devices
Roon Remote:
Roon 2.0, Build 1128, Macbook Pro 2021, M1, 16GB RAM, MacOS 12.4, connected by wifi
Number of Tracks in Library
150,604
Description of Issues
I updated to Roon 2.0 a few days ago and have left my Roon Core running during this time to see how it would react. I’m only running Roon on this machine along with a few small widgets that were pre-installed.
While it’s initially using less memory than 1.8, I’m noticing some strange numbers on the Activity Monitor. In particular, the number of ports being used keeps climbing the longer it runs. I’m also noticing that rpcsvchost is using a lot of memory, and getting consistently higher.
Is this normal?
After 2 days, prior to restart:
roon - 3.10 GB memory used - 74,000 ports
rpcsvchost - 1.22 GB memory used - 47 ports
raatserver - 229 MB memory used - 168 ports
cached files - 5.28 GB memory used
total memory used 10.63 GB
soon after I restarted
roon - 3.46 GB memory used - 765 ports
rpcsvchost - not running
raatserver - 213 MB memory used - 149 ports
cached files - 6.26 GB memory used
total memory used 8.04 GB
The number of ports used on my Mac Mini M1 continues to rise anytime I have it turned on. Earlier this week I had left it on for maybe 3 days and it was up over 90,000 ports used. This is visible on the Activity Monitor.
I’m not really familiar with how ports work, but this seems like a really high number. Is it something to be concerned about?
My post is certainly not urgent and I know there are a significant number of high priority issues with the recent update, but does anyone have thoughts on what might be happening here?
see the same thing here with an Intel Mac Mini and macOS 12.6. Roon also uses a lot of memory - over 1G when it’s running for a while with those thousands of ports open.
Those are Mach kernel ports (macOS is based on Mach) and are used by the kernel for interprocess communication. That number does seem excessive and might constitute a “Mach port leak”.
Doing a Google search on “macOS and Mach port leaks” yields a lot of good information.
Let’s hope the folks in Roon Support see this and check to see if there is a bug causing Mach port leaks.
Just checked on my core and it is using 50,000 ports (Roon 2.0, 2018 mini, Monterey 12.5). However (and I really hate to jinx it), the memory leak seems to have disappeared after upgrading to 2.0 .
I think I’m having something similar happen on my Intel Mac mini with Roon 2.0. After a couple of days, I notice that Roon becomes slow and unresponsive and is burning around 120% CPU usage. Quitting Roon and relaunching it temporarily solves the issue.
BTW: I did run a Sample on the Roon process when it was in this bad state, so Roon support folks let me know if you want me to upload it (its a couple of MB worth of backtrace).
Are you sure there is an issue? I said the ports used seemed excessive but I don’t know that it is. @support should certainly look the post I made above and check to see if they are having a problem or not…
I don’t know anything about how memory ports work, and it’s been difficult to research because this seems very uncommon. If 100,000+ ports are being utilized by Roon, could this have a negative effect on the computer?
I don’t know that it’s a major concern, but I’d like to learn more about what’s taking place. Also, is this limited to a few users or does it happen with everyone?
They are not memory ports. The number of kernel ports used does not appear to correlate to memory used. HQPlayer is also using a large number of kernel ports on my M1 Mac mini. It may be that using a lot of kernel ports is perfectly normal for Roon and HQPlayer. This is why I suggested @support should take a look at my first post in this thread and check to see if all is as it should be.
Personally, I would not worry about it until I actually experienced a problem. Roon has has been nothing but stellar running natively on my M1 Mac mini!! I have had no issues whatsoever.
Are you still seeing this issue with the most recent Roon build or has there been any change in behavior? If you are still seeing this issue, can you please take a Sample of the Roon process, upload the log to the below link, and let us know once uploaded? Thanks!
Thanks for the response. I’m still seeing this behavior, although I can’t say that it’s had any negative effect on performance. If I restart the computer, everything goes back to zero and starts counting up again. I mostly find it curious and would like to see if it’s normal behavior or a sign of other issues.
I’ll be happy to take a sample of the Roon process when I have some time over the weekend.
While we are not finding definitive answers from Mac forums, we have deduced that the ports are similar to the CPU time in the activity monitor in that they are cumulative in nature. You can look at the sample when you monitor the process that shows the files in use and of course, there are nowhere near the roughly 250k ports opened. We’re still testing this, but in my own testing, I saw no negative impact on performance or functionality, which bolsters the idea that the numbers are cumulative.
.
