Roon 2.0 crashes on Late 2012 Mac mini

Support
1

Roon Core Machine

Mac mini (Late 2012)
2.5 GHz Dual-Core Intel Core i5
16 GB 1600 MHz DDR3

Networking Gear & Setup Details

Ubiquiti EdgeRouter 5 PoE
Netgear Orbi RBR20
Netgear Orbi RBS20

Connected Audio Devices

AirPlay 2 and Chromecast

Number of Tracks in Library

31,690 tracks

Description of Issue

[Reopening former ticket from Sept. 22]

Since installing Roon 2.0 on my Roon Core back in September, I find that the Roon app on the Core on my Mac mini regularly crashes after a few minutes, even when I’m not playing music (the app may, however, be indexing newly added songs as they’re downloading to my machine unattended).

I installed Roon Core on a newer Mac model (MacBook Pro, 13-inch, 2017) and the problem went away. Because it is a laptop, it’s not an ideal platform to run Roon Core from. So today, I reinstalled a fresh copy on the Mac mini and restored from backup. The problem has reemerged. Can you help me troubleshoot?

2

A fellow user here, but what MacOS version are you running on your 2012 mini? Are you getting any specific error message when Roon crashes?

3

@Robert_F - thanks for the quick response. The Mac mini runs the latest supported macOS version for its hardware, which is 10.15.7.

In terms of error message, no, it silently crashes. After about 1-2 minutes, the “Problem Report” window pops up with its 3000+ lines of diagnostic info. The first couple of lines read:

Process: Roon [80795]
Path: /Applications/Roon.app/Contents/MacOS/Roon
Identifier: com.roon.Roon
Version: 1.0 (1.0)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Roon [80795]
User ID: 501

Date/Time: 2023-01-02 12:38:24.380 -0500
OS Version: Mac OS X 10.15.7 (19H2026)
Report Version: 12
Anonymous UUID: 22B20C21-7B55-1E5D-B4F2-9FCF941EB0BB

Time Awake Since Boot: 3200000 seconds

System Integrity Protection: enabled

Crashed Thread: 72 .NET ThreadPool Worker

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

Application Specific Information:
abort() called

4

Here’s the crash report from last night:

Process: Roon [84302]
Path: /Applications/Roon.app/Contents/MacOS/Roon
Identifier: com.roon.Roon
Version: 1.0 (1.0)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Roon [84302]
User ID: 501

Date/Time: 2023-01-03 05:22:13.049 -0500
OS Version: Mac OS X 10.15.7 (19H2026)
Report Version: 12
Anonymous UUID: 22B20C21-7B55-1E5D-B4F2-9FCF941EB0BB

Time Awake Since Boot: 3300000 seconds

System Integrity Protection: enabled

Crashed Thread: 67 .NET ThreadPool Worker

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000700008543fe8
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Bus error: 10
Termination Reason: Namespace SIGNAL, Code 0xa
Terminating Process: exc handler [84302]

VM Regions Near 0x700008543fe8:
Stack 00007000084c1000-0000700008543000 [ 520K] rw-/rwx SM=COW thread 9
→ Stack Guard 0000700008543000-0000700008544000 [ 4K] —/rwx SM=NUL
Stack 0000700008544000-00007000085c6000 [ 520K] rw-/rwx SM=COW

5

What roon 2.0 build number are you using?

6

Roon version 2.0 (build 1182)

7

Latest crash report:

Process: Roon [3530]
Path: /Applications/Roon.app/Contents/MacOS/Roon
Identifier: com.roon.Roon
Version: 1.0 (1.0)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Roon [3530]
User ID: 501

Date/Time: 2023-01-03 11:59:25.756 -0500
OS Version: Mac OS X 10.15.7 (19H2026)
Report Version: 12
Anonymous UUID: 22B20C21-7B55-1E5D-B4F2-9FCF941EB0BB

Time Awake Since Boot: 3300000 seconds

System Integrity Protection: enabled

Crashed Thread: 58 .NET ThreadPool Worker

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

Application Specific Information:
abort() called

8

I have the same issue with Roon 2.0 (build 1182) on a MacBook Pro with M1 Pro, 32Gb RAM, 2TB SSD, running Ventura 13.1…

Translated Report (Full Report Below)

Process: Roon [97307]
Path: /Applications/Roon.app/Contents/MacOS/Roon
Identifier: com.roon.Roon
Version: 1.0 (1.0)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 502

Date/Time: 2022-12-28 16:09:20.5271 -0700
OS Version: macOS 13.1 (22C65)
Report Version: 12
Anonymous UUID: 62EBEF5E-2A2F-DC00-B43C-34697A94152A

Time Awake Since Boot: 1100000 seconds

System Integrity Protection: enabled

Crashed Thread: 72 .NET ThreadPool Worker

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

Application Specific Information:
abort() called

Time Awake Since Boot: 1100000 seconds

System Integrity Protection: enabled

Crashed Thread: 67 .NET ThreadPool Worker

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

Application Specific Information:
abort() called

sometimes it crashes while playing a track, sometimes when it is idle… I rebooted, then about 20 minutes later is crashed again…

Translated Report (Full Report Below)

Process: Roon [97626]
Path: /Applications/Roon.app/Contents/MacOS/Roon
Identifier: com.roon.Roon
Version: 1.0 (1.0)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 502

Date/Time: 2022-12-28 16:26:49.5508 -0700
OS Version: macOS 13.1 (22C65)
Report Version: 12
Anonymous UUID: 62EBEF5E-2A2F-DC00-B43C-34697A94152A

9

Any thoughts/advice?

10

See
https://community.roonlabs.com/t/roon-causing-kernel-panic-on-mac-mini/230242/2?u=ged_hickman1

11

Hey @Omar_Chaudhry,

Thanks for your patience while we work through each thread. I’m sorry to hear you’re running into issues with your Mac OS core crashing.

This trace lines up with a known issue we’re actively working on now, as @ged_hickman1 has just shared a link to above (thanks Ged!)

The only workaround at this time would be to set up Roonserver on your core. If you’d like to give this a try while we work on a fix, Wes does a great job breaking down the step-by-step here :

I will certainly keep you in the loop as we continue to work out a solution!

2 Likes
14

Thanks, @ged_hickman1 and @benjamin ! For those looking for the exact post, here it is:

15

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.