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).
I have moved your post to its own thread as Roon prefer to work on one item at a time.
Thank you for your patience and understanding
Hi,
I am also on Monterey 12.3 and Roon 1.8 (918) on an M1pro MBP. But no issues so far.
Core is a Synology NAS. So it probably isn’t a general problem.
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:
>Crashed Thread: 39 Thread Pool Worker
>Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00000001300018d8
Exception Codes: 0x0000000000000002, 0x00000001300018d8
Exception Note: EXC_CORPSE_NOTIFY
>Thread 39 Crashed:: Thread Pool Worker
0 ??? 0x7ff89e5fa940 ???
1 libsystem_kernel.dylib 0x7ff80dfef00e __pthread_kill + 10
2 libsystem_pthread.dylib 0x7ff80e0251ff pthread_kill + 263
3 libsystem_c.dylib 0x7ff80df70d24 abort + 123
4 Roon 0x102769a4b altstack_handle_and_restore + 235
5 Roon 0x102825d36 mono_arch_patch_callsite + 134
6 Roon 0x10280d9c6 common_call_trampoline + 2166
7 Roon 0x10280d100 mono_magic_trampoline + 96
8 ??? 0x10df0d393 ???
9 ??? 0x1300018e3 ???
10 mscorlib.dll.dylib 0x110bcffb1 System_Runtime_CompilerServices_AsyncMethodBuilderCore_MoveNextRunner_InvokeMoveNext_object + 177
11 mscorlib.dll.dylib 0x110a35853 System_Threading_ExecutionContext_Run_System_Threading_ExecutionContext_System_Threading_ContextCallback_object_bool + 67
12 mscorlib.dll.dylib 0x110a7299b System_Threading_Tasks_AwaitTaskContinuation_RunOrScheduleAction_System_Action_bool_System_Threading_Tasks_Task_ + 123
13 mscorlib.dll.dylib 0x110a69a23 System_Threading_Tasks_Task_FinishContinuations + 307
14 mscorlib.dll.dylib 0x110a67fc1 System_Threading_Tasks_Task_FinishStageThree + 129
15 mscorlib.dll.dylib 0x110bcffb1 System_Runtime_CompilerServices_AsyncMethodBuilderCore_MoveNextRunner_InvokeMoveNext_object + 177
16 mscorlib.dll.dylib 0x110a35853 System_Threading_ExecutionContext_Run_System_Threading_ExecutionContext_System_Threading_ContextCallback_object_bool + 67
17 mscorlib.dll.dylib 0x110a7299b System_Threading_Tasks_AwaitTaskContinuation_RunOrScheduleAction_System_Action_bool_System_Threading_Tasks_Task_ + 123
18 mscorlib.dll.dylib 0x110a69a23 System_Threading_Tasks_Task_FinishContinuations + 307
19 mscorlib.dll.dylib 0x110a67fc1 System_Threading_Tasks_Task_FinishStageThree + 129
20 mscorlib.dll.dylib 0x110bcffb1 System_Runtime_CompilerServices_AsyncMethodBuilderCore_MoveNextRunner_InvokeMoveNext_object + 177
21 mscorlib.dll.dylib 0x110a35853 System_Threading_ExecutionContext_Run_System_Threading_ExecutionContext_System_Threading_ContextCallback_object_bool + 67
22 mscorlib.dll.dylib 0x110a7299b System_Threading_Tasks_AwaitTaskContinuation_RunOrScheduleAction_System_Action_bool_System_Threading_Tasks_Task_ + 123
23 mscorlib.dll.dylib 0x110a69a23 System_Threading_Tasks_Task_FinishContinuations + 307
24 mscorlib.dll.dylib 0x110a67fc1 System_Threading_Tasks_Task_FinishStageThree + 129
25 mscorlib.dll.dylib 0x110bcffb1 System_Runtime_CompilerServices_AsyncMethodBuilderCore_MoveNextRunner_InvokeMoveNext_object + 177
26 mscorlib.dll.dylib 0x110a35853 System_Threading_ExecutionContext_Run_System_Threading_ExecutionContext_System_Threading_ContextCallback_object_bool + 67
27 mscorlib.dll.dylib 0x110a7299b System_Threading_Tasks_AwaitTaskContinuation_RunOrScheduleAction_System_Action_bool_System_Threading_Tasks_Task_ + 123
28 mscorlib.dll.dylib 0x110a69a23 System_Threading_Tasks_Task_FinishContinuations + 307
29 mscorlib.dll.dylib 0x110a67fc1 System_Threading_Tasks_Task_FinishStageThree + 129
30 mscorlib.dll.dylib 0x110bcffb1 System_Runtime_CompilerServices_AsyncMethodBuilderCore_MoveNextRunner_InvokeMoveNext_object + 177
31 mscorlib.dll.dylib 0x110a35853 System_Threading_ExecutionContext_Run_System_Threading_ExecutionContext_System_Threading_ContextCallback_object_bool + 67
32 mscorlib.dll.dylib 0x110a7299b System_Threading_Tasks_AwaitTaskContinuation_RunOrScheduleAction_System_Action_bool_System_Threading_Tasks_Task_ + 123
33 mscorlib.dll.dylib 0x110a69a23 System_Threading_Tasks_Task_FinishContinuations + 307
34 mscorlib.dll.dylib 0x110a67fc1 System_Threading_Tasks_Task_FinishStageThree + 129
Same here, on a Mac mini M1 2020
Core is a ROCK install on a NUC
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.
The server is on a Xeon linux box, and working as expected. Thankfully the iOS client works.
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.
Bob
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
Same here. MacOS 12.3.1 on a Mac Mini M1
System Integrity Protection: enabled
Crashed Thread: 38 Thread Pool Worker
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_PROTECTION_FAILURE at 0x000000012c42f1c8
Exception Codes: 0x0000000000000002, 0x000000012c42f1c8
Exception Note: EXC_CORPSE_NOTIFY
VM Region Info: 0x12c42f1c8 is in 0x12c42f000-0x12c430000; bytes after start: 456 bytes before end: 3639
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
Rosetta Generic 12c42b000-12c42c000 [ 4K] rw-/rwx SM=PRV
GAP OF 0x3000 BYTES
---> VM_ALLOCATE 12c42f000-12c430000 [ 4K] r-x/rwx SM=COW
VM_ALLOCATE 12c430000-12c431000 [ 4K] r-x/rwx SM=COW
Application Specific Information:
abort() called
Thread 0:: tid_103 Dispatch queue: com.apple.main-thread
0 ??? 0x7ff898a16940 ???
1 libsystem_kernel.dylib 0x7ff8084049b6 semaphore_wait_trap + 10
2 Roon 0x10070a8a8 mono_thread_info_wait_for_resume + 24
3 Roon 0x100707369 mono_threads_state_poll_with_info + 121
4 Roon 0x1007079cf mono_threads_enter_gc_unsafe_region_unbalanced_with_info + 143
5 Roon 0x100503097 mono_magic_trampoline + 55
6 Roon 0x100503d15 mono_aot_trampoline + 181
7 ??? 0x10bc0cb13 ???
8 BrooEngine.dll.dylib 0x110d32627 Broo_Engine_LabelBase_OnLayout_single_single_int_single_single_single_single_single_single_single_single + 1831
9 BrooEngine.dll.dylib 0x110cdb643 Broo_Engine_Widget_Layout_single_single_int_single_single_single_single_single_single_single_single + 531
10 BrooEngine.dll.dylib 0x110ce8887 Broo_Engine_BoxPanel_OnLayout_single_single_int_single_single_single_single_single_single_single_single + 5335
11 BrooEngine.dll.dylib 0x110cdb643 Broo_Engine_Widget_Layout_single_single_int_single_single_single_single_single_single_single_single + 531
12 BrooEngine.dll.dylib 0x110ce8887 Broo_Engine_BoxPanel_OnLayout_single_single_int_single_single_single_single_single_single_single_single + 5335
13 BrooEngine.dll.dylib 0x110cdb643 Broo_Engine_Widget_Layout_single_single_int_single_single_single_single_single_single_single_single + 531
14 BrooEngine.dll.dylib 0x110d0f682 Broo_Engine_StackPanelBase_OnLayout_single_single_int_single_single_single_single_single_single_single_single + 2242
15 BrooEngine.dll.dylib 0x110cdb643 Broo_Engine_Widget_Layout_single_single_int_single_single_single_single_single_single_single_single + 531
16 BrooEngine.dll.dylib 0x110d0f682 Broo_Engine_StackPanelBase_OnLayout_single_single_int_single_single_single_single_single_single_single_single + 2242
17 BrooEngine.dll.dylib 0x110cdb643 Broo_Engine_Widget_Layout_single_single_int_single_single_single_single_single_single_single_single + 531
18 BrooEngine.dll.dylib 0x110d0b9cd Broo_Engine_WindowWidget_DoLayout + 8957
19 BrooEngine.dll.dylib 0x110d51569 Broo_Engine_Engine_Update + 777
20 BrooEngine.dll.dylib 0x110d516ff Broo_Engine_Engine_GuiMainLoop + 47
21 ??? 0x10bc90d0b ???
22 ??? 0x10bc90f31 ???
23 Roon 0x100500d92 mono_jit_runtime_invoke + 2354
24 Roon 0x1006361d7 mono_runtime_invoke_checked + 135
25 Roon 0x10063e69e do_exec_main_checked + 94
26 Roon 0x1004555de mono_jit_exec + 414
27 Roon 0x100458845 mono_main + 9397
28 Roon 0x10040c5cc xamarin_main + 1116
29 Roon 0x10040d414 main + 36
30 dyld 0x200e7151e start + 462
Thread 1:: com.apple.rosetta.exceptionserver
0 runtime 0x7ff7ffe5c944 0x7ff7ffe58000 + 18756
1 runtime 0x7ff7ffe6b100 0x7ff7ffe58000 + 78080
2 runtime 0x7ff7ffe6bed0 0x7ff7ffe58000 + 81616
Thread 2:
0 runtime 0x7ff7ffe7a814 0x7ff7ffe58000 + 141332
Thread 3:
0 runtime 0x7ff7ffe7a814 0x7ff7ffe58000 + 141332
Thread 4:
0 runtime 0x7ff7ffe7a814 0x7ff7ffe58000 + 141332
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.
Yup. Still extremely crashy on Mac Studio Ultra. Additionally, it is not exiting cleanly every time when it does crash.
$ ps -ef | grep -i roon
501 11185 1 0 Thu04PM ?? 0:00.00 /Applications/Roon.app/Contents/MacOS/Roon
501 11265 1 0 Thu04PM ?? 0:00.00 /Applications/Roon.app/Contents/MacOS/Roon
501 18389 1 0 4:13PM ?? 0:00.00 /Applications/Roon.app/Contents/MacOS/Roon
501 18632 1 0 4:14PM ?? 0:00.00 /Applications/Roon.app/Contents/MacOS/Roon
501 18636 1 0 4:14PM ?? 0:00.00 /Applications/Roon.app/Contents/MacOS/Roon
501 18776 1 0 4:15PM ?? 0:00.00 /Applications/Roon.app/Contents/MacOS/Roon
501 19010 1 0 4:17PM ?? 0:00.00 /Applications/Roon.app/Contents/MacOS/Roon
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).