Roon has always been stable but since the latest update (version 1.8, build 918) it crashes nearly every time when I launch the application.
I am talking of the Roon macOS client.
Two things have changed in the last days: Apple has submitted a new OS version, Monterey 12.3. About the same time there was the Roon update.
As Roon is the only application on my system (Mac M1) that crashes, I think it is something in Roon (or the underlying Mono platform).
It’s Roon. I updated to 12.3 a couple of hours before updating Roon to 918, and Roon Client was rock solid, as it’s always been. As soon as I upgraded to 918 Roon started crashing on launch. For me, it’s about once every third launch, and the problem report indicates the following:
Also problems here with Roon 918 and Monterey 12.3 on a MacMiniM1 8GB. Massiv memory leaking leads to regular crashes. Check your activity monitor for memory consumption of Roon.
I guess I get to join the me too club on this one. It just took waaaay too many tries to get Roon client started on my Mac Studio Ultra running macOS 12.3.
Just updated to the latest version: 1.8 (build 923) for the macOS Roon client and ROCK.
The problem stays: it is nearly impossible to start the Roon client without crashing:
Process: Roon [25813]
Path: /Applications/Roon.app/Contents/MacOS/Roon
Identifier: com.roon.Roon
Version: 1.0
Code Type: X86-64 (Translated)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2022-03-28 22:54:10.0009 +0200
OS Version: macOS 12.3 (21E230)
Report Version: 12
Anonymous UUID:
Sleep/Wake UUID:
Time Awake Since Boot: 54000 seconds
Time Since Wake: 2421 seconds
System Integrity Protection: enabled
Crashed Thread: 45 Thread Pool Worker
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000144573d30
Exception Codes: 0x0000000000000002, 0x0000000144573d30
Exception Note: EXC_CORPSE_NOTIFY
VM Region Info: 0x144573d30 is in 0x144573000-0x144574000; bytes after start: 3376 bytes before end: 719
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
VM_ALLOCATE 14456f000-144570000 [ 4K] r-x/rwx SM=COW
GAP OF 0x3000 BYTES
---> VM_ALLOCATE 144573000-144574000 [ 4K] r-x/rwx SM=COW
VM_ALLOCATE 144574000-144575000 [ 4K] r-x/rwx SM=COW
Same here. macOS Catalina and iMac @ Intel - Roon Core. Memory leaks, so huge, system crashes (sic!), or freezing (kill Core and problems out). No solution here. I try everything. Different topic on support describes my story.
Yeah, build 923 of the Roon Client is still rather difficult to get started on a Mac Studio Ultra with macOS 12.3.1. It either beachballs and requires a forced quit or SIGABRTs a few seconds after launch. Sometimes I only have to try launching a 2 times, others it takes upwards of 10 attempts.
Same here, Mini M1 2020.
I installed Roon again to see if the 12.3.1 update was a solution. the first 2 times I started Roon it seemed ok, this morning it took 7 tries to get Roon Running again.
I thought I’d managed to fix this, but I’m also having exactly the same issue - it can take multiple attempts to launch Roon client (Mac mini M1 running macOS 12.3.1). Once it’s up and running, it’s stable, it’s just launching it that’s the issue.
>Process: Roon [41920]
Path: /Applications/Roon.app/Contents/MacOS/Roon
Identifier: com.roon.Roon
Version: 1.0
Code Type: X86-64 (Translated)
Parent Process: launchd [1]
User ID: 501
>
>Date/Time: 2022-04-02 10:55:02.0717 +0100
OS Version: macOS 12.3.1 (21E258)
Report Version: 12
Anonymous UUID: FE21C549-9218-179B-E17B-0F0EE72EAFB4
>
>
>Time Awake Since Boot: 4100 seconds
>
>System Integrity Protection: enabled
>
>Crashed Thread: 30 Thread Pool Worker
>
>Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000135f521c8
Exception Codes: 0x0000000000000002, 0x0000000135f521c8
Exception Note: EXC_CORPSE_NOTIFY
>
>VM Region Info: 0x135f521c8 is in 0x135f52000-0x135f53000; bytes after start: 456 bytes before end: 3639
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
VM_ALLOCATE 135f4f000-135f50000 [ 4K] r-x/rwx SM=COW
GAP OF 0x2000 BYTES
---> VM_ALLOCATE 135f52000-135f53000 [ 4K] r-x/rwx SM=COW
VM_ALLOCATE 135f53000-135f54000 [ 4K] r-x/rwx SM=COW
Add me to the list, it’s virtually impossible to get Roon to open as a remote on my Mac mini M1. I’ve also experienced high memory usage. I tried uninstalling everything and reinstalling but nothing changed. Eagerly awaiting a solution.
Update: I just tried reinstalling Rosetta 2 and it seems to have fixed the problem. I remembered reading on MacRumors that software updates can sometimes mess with the Rosetta install. For those willing to try it you can re-install Rosetta 2 with a terminal command. This only applies to M1 Macs.
softwareupdate --install-rosetta
It will ask you to agree when you execute this command in Terminal.
Update 2: Roon is still crashing on launch intermittently which is better than before but it’s still not working well.
Requiring something like killall -9 Roon to be executed to clean up. These ghost processes were making successful launches unable to connect to the server.
I tried the recent macOS 12.4 beta and the experience with crashing seems to have subsided somewhat. It’s not perfect but certainly better than it was. I’m also running a hackintosh and Roon works perfectly as a remote on that machine.
Build 931… took more than 10 launches to get the client running on macOS 12.3.1 on Studio Ultra. No real change since build 918. Just abort signals and beachballs all the way down.
Same issue here with MacBook Pro with build 931. Always crashing after ten minutes. I’ve re installed Roon and then I could listen one hour to my music, then Roon crashes again. Private relay is turned off.
Add me to the list. Mac Studio M1 Max and Roon crashes when start 1 out 10 times. However, it never crashes while running, only 1 out 10 when starting. Also I always get the “Searching for Core” screen for a couple of seconds then it connects with the core (ROCK on NUC 10i7FNHN1).