I just started a two week trial and I’m experiencing the exact same issue.
macOS Mojave
Version 10.14.5
Mac mini (2018)
As soon as I launch Roon, all six cores are immediately pegged. Even if I’m just sitting at the login screen.
I just started a two week trial and I’m experiencing the exact same issue.
macOS Mojave
Version 10.14.5
Mac mini (2018)
As soon as I launch Roon, all six cores are immediately pegged. Even if I’m just sitting at the login screen.
Hello @Dan_Backman and @EvilGnome6,
Thanks for the reports, I’ve forwarded this information to the QA Team for investigation.
Some further info that would be helpful:
Here are some diagnostic tests that would help us track down this issue:
-John
Information:
Troubleshooting:
John,
Diagnostics:
I can also run a process trace in Activity Monitor and send that to you if you can provide me with a direct email address to submit the data.
Interesting to note that Mike_deCock and I have several things in common:
Audio devices:
$ system_profiler SPAudioDataType
Audio:
Devices:
DisplayPort:
Manufacturer: Apple Inc.
Output Channels: 2
Current SampleRate: 48000
Transport: DisplayPort
Output Source: LED Cinema Display
DisplayPort:
Manufacturer: Apple Inc.
Output Channels: 2
Current SampleRate: 48000
Transport: DisplayPort
Output Source: LG HDR 4K
Display Audio:
Default Input Device: Yes
Default Output Device: Yes
Default System Output Device: Yes
Input Channels: 1
Manufacturer: Apple Inc.
Output Channels: 2
Current SampleRate: 48000
Transport: USB
Input Source: Default
Output Source: Default
Mac mini Speakers:
Manufacturer: Apple Inc.
Output Channels: 2
Current SampleRate: 48000
Transport: Built-in
Output Source: Mac mini Speakers
Here’s an interesting observation. If I have the Roon Bridge Running before I launch the Roon app, I don’t experience the high CPU usage.
Hello @EvilGnome6 & @Dan_Backman,
Thank you both for the observations, I have added this information to the QA ticket. I will be sure to follow up when QA has made an assertion, I know they are actively working on this.
-John
Hello @Dan_Backman & @EvilGnome6,
If you go to your ~/Library/ folder, you should see a folder named “Roon”. Could you try renaming this folder to “Roon_old”, then restarting Roon and reporting if you see any differences in behavior?
-John
Hi John,
I renamed the Roon folder as instructed and restarted Roon. It created a new folder and the CPU usage spiked immediately.
Edit: This was with the Roon Bridge turned off. When it’s on, I don’t experience the high utilization.
This did not solve the problem. I moved the directory as you suggested, and the app asked me to acknowledge the terms and conditions and reselect my roon server.
Once the app launched, I am having exactly the same problem with high CPU utilization as before. No change.
Any updates on this? The symptoms seem 100% consistent on my client, and are easy to replicate. Is there anything else we can do to help troubleshoot this?
Thanks…
Hello @Dan_Backman,
Could you use the “Sample Process” feature in Activity Monitor to save logs of Roon as well as RAATServer when they are in this broken state? Once you have saved the logs as text files, please upload them to a service like Firefox Send so we can pass them along to the development team.
-John
Hello @john ,
I have the same issue (Mac Mini 2018 + very high cpu load)
I created a logfile and sent it via Firefox send to your support (contact panel).
But I think the 24h expired.
How can I contact you?
Hi @Tim_Surber,
Thank you for your interest here. I have just followed up via private message for next steps and this message should appear as a green “1” in the top right-hand corner of this site.
Update:
The high CPU usage issue on this 6-core Mac Mini seem to have been solved by the latest update to macOS (10.14.6)
For the other people on this thread, can you confirm that this OS update seems to have fixed the issue?
No, still the same for me.
10.14.6 update does not resolve issue on my 2018 mac mini
Looks like you guys are right. While the update made things better, if I leave the app running, it will eventually get back into the same high CPU state (even after the 10.14.6 update). Looks like there is still something going on in the Roon.app
I was strongly considering upgrading my mac mini to a 2018 one. Is this issue present in all of them or is it only noted in an unlucky few?
Same issue with 2018 Mac Mini here.
It’s espcially irritating because if I close Roon to avoid the noisy fan caused by Roon unnecessarily smashing CPU usage, on restart it forces a library rescan from my NAS which takes forever. I’m starting to think the high CPU usage has something to do with the library scan, but even after the scan is finished, the CPU is still at peak usage and fan is being noisily overworked. I don’t have a single other apllication that causes this behaviour.
3GHz i5 running 10.14.6 and had same issue before upgrading OS
Even with the library disabled in settings so that Roon has no music available (eliminating the library scan on restart), after restart still the same crazy high CPU usage.