Mac Mini M1
Google Nest Ethernet
(RP4 with Ropiee XL with USB to DAC)
21000
Well, the Roon core has worked well for a long time on my Mac Mini. The last week or two, I have gotten up in the morning to find Roon has crashed and there is an Apple crash report on the screen. Something like 4 or 5 times. Each time I restart it and it seems to work OK. I haven’t fiddled with the Mini in quite some time so I suppose the only change is the latest Roon update.
Copy and post the Apple crash report?
Well, another surprise. This morning Roon crashed again. But this time it was my remote player (an iMac) but the core was still running. Note that only Roon was affected in both cases.
Here’s the Apple report — the last line keeps repeating so I excluded it.
This time, also…my local node (Google Nest router) was offline. I had to reboot it. I suspect something is up with the node.
Process: Roon [89834]
Date/Time: 2023-03-13 19:50:49.6076 -0400
Time Awake Since Boot: 300000 seconds
System Integrity Protection: enabled
Crashed Thread: 30 .NET ThreadPool Worker
Exception Type: EXC_CRASH (SIGABRT)
Application Specific Information:
Thread 0:: Dispatch queue: com.apple.main-thread
Seems like this known issue, thread with Roon investigation:
Since upgrading to Roon 2.0, my Roon core running on a 2018 8GB Mac Mini constantly crashes, whether or not I am using Roon. I understand there are going to be issues, but this does not seem to me to be an uncommon or antiquated setup. If it is no longer supported, would’ve been nice for the upgrade program to have noticed. Please advise if there is a quick fix, or if I just have to wait until the next patch.
Looks similar but that is from September…mine just started doing this a week or so ago. It was one before that.
Another strange occurrence is when I restarted Roon on the player, the Core was gone. I went to the computer with the core and got this
But when I logged on again…everything was once again running fine.
(until tonight)
This issue in the other thread has been going on for a long time, is not fixed yet, and seems to affect only some people and machines, so it’s possible that it didn’t affect you in the past and now does. Which would be particularly interesting to investigate what changed. I think Roon has had problems reproducing the issue and hence pinning it down
Also interesting is one Mac is an M1 (mini) and the other is an Intel (iMac) - and both crashed.
Wayward pointer somewhere?
Just did the most recent Roon update and the core crashed
Process: Roon [26260]
Date/Time: 2023-03-15 15:53:26.3163 -0400
Time Awake Since Boot: 1200000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Application Specific Information:
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
Same here. Roon Core iMac @ Intel on Catalina and crash 2-4 times per month. MBA @ M1 and Core/Remote/Bridge also one per week comm: Roon not response, must relaunch software.
With 1.6 and 1.7 if im not wrong Roon was rock stable. With 1.8 sometimes crash, after 2.x crash as hell (end-ponts also lost connection with Core!). Unstable. No fun, no good, I want stable soft!
Just did the latest update and the remote iMac player updated successfully, but the core crashed.
Process: Roon [63017]
Date/Time: 2023-03-21 08:31:58.1198 -0400
Time Awake Since Boot: 1700000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Application Specific Information:
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
