Mac mini locked up and crashed first day of Roon Use - Help Please

Mac mini (2018)

  • 3 GHz 6-Core Intel Core i5
  • 16gB Memory
  • 10.15.6 Beta (19G60d)
  • Roon 1.7 (Build 571)

Mac on Wi-fi

  • Amplifi HD Router
  • 100mB connection

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

Eclipse TD-M1 active DAC/Speakers - connected by USB from Mac to Speaker - working perfectly
Sonos Playbar found & connected via network but not in use
Apple TV4 - Sonos Playbar found via network but not in use
Roon Remote on iPhone - connected but not in use
Playing from local files and Qobuz

Problem
This was my first install of Roon yesterday @ around 15.45
All OK except machine ran very hot in use during the afternoon
First time I have ever heard Mac Mini fans running
Noted Roon very high CPU usage over 100% and higher
(CURRENT TODAY Process (count) Source CPU Roon Roon Labs LLC 105.00 %)
A couple of times the cursor got very laggy / jumpy
Left machine running playing music with screensaver around 18.00
Later returned to machine and screensaver running but locked in place, cannot get back to desktop Shortly after machine reverted to a powered blank screen @ around 19.15
Nothing I could do would get me back to a working Mac
Had to hard crash/restart machine with power button

TODAY - restarted OK, but after launching Roon fans spun up immediately
CURRENT TODAY Process (count) Source CPU Roon Roon Labs LLC 105.00 %

I have full Roon logs but CAN SEE NO WAY TO UPLOAD DOCS? what am I missing?

Process: Roon [87975]
Path: Roon
Identifier: com.roon.Roon
Version: 1.0
Code Type: X86-64 (Native)
Parent Process: launchd [1]
Responsible: Roon [87975]
User ID: 501

Date/Time: 2020-07-06 19:13:58.579 +1000
OS Version: Mac OS X 10.15.6 (19G60d)
Report Version: 12
Bridge OS Version: 4.6 (17P56058a)
Anonymous UUID: CD6851CD-A4F0-BED9-F028-29B9C457E9B2

Sleep/Wake UUID: 0ADF8D0F-CB0C-44BB-B6C0-065D26916586

Time Awake Since Boot: 100000 seconds
Time Since Wake: 41000 seconds

System Integrity Protection: enabled

Crashed Thread: 0 tid_307 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
*** Terminating app due to uncaught exception ‘NSInternalInconsistencyException’, reason: ‘CGSGetSurfaceBinding failed with 268435459’
abort() called
terminating with uncaught exception of type NSException

Playing same 24/96 Handel streaming music, Qobuz uses about 3% CPU, Audirvarna uses under 1%, Roon using between 90% and 150% - something not right.

Have you installed the full Roon package or the GUI-less Roon Server on your Mac Mini? I would try the Roon Server and use the Remote on the iPhone or any other PC or Mac to interface with the server. There have also been reports that shutting down the WiFi and reconnecting it again resolves the high CPU load in Macs, at least temporarily.

Full Roon package on my main working Mac. Such a shame as that is how I want to use it on my desktop system. Will try the remote option on a spare machine. Think I am going back to Audirvarna until this is fixed. It’s a long time since some new software has crashed my Mac )-: Cheers Robert

Hi @Robert_Follis,

We don’t typically perform any testing on Beta OSs, so please do be aware that this may be a cause of the issue. If you have a Mac running a stable version of the OS, it might be better to try to have Roon installed there.

Can you please upload the full log set to the link I PM’d you?

I would instead try the Server version on another machine, not running the beta and leave just the Roon client running on the beta machine, please see Running Roon as a Remote Guide.

While it’s important for you to point out that Roon is not being tested on Beta versions of supported OS, it would be fair and helpful if you also acknowledged that there have been many more reports of Mac users with very similar symptoms. I am still on MacOS 10.14 on my Macbook Pro used as Remote, and have experienced the same… albeit not since the last Roon update.

So this may have to do with the OP running a beta OS, or it may not.

Hi @Andreas_Philipp1,

We have acknowledged that this is an issue and one that we’re looking into, please see:

I was more-so referring to this error that the user posted:

I suspect this one in particular might be due to the BetaOS.

1 Like

Hi all and thanks for help. I also have a 2012 Mac mini and will load Roon on that and see what happens. Cheers Robert

1 Like