Core Machine (Operating system/System info/Roon build number)
Hello. I have Roon installed on my Mac Pro, MacOS Mojave10.14.6. Roon 1.7 build 537
It crashes constantly, as in every day. I can send you the details/log from MacOS if you wish.
Which info do you need further to troubleshoot this problem?
Regards,
Willem Keller
Netrherlands
Exactly what model MacPro spec etc etc
MacOS 5,1 mid 2012
2 x 3,06GHz 6-core Intel Neon
48 GB 1333MHz DDR3 RAM
PCIe bootdisk
SSD datadisk
AMD Radeon HD7950 3GB GPU
Running Mojave 10.14.6
Hello @Willem_Keller, and welcome to the community! What’s happening when Roon crashes? Are you using Roon actively at the time? Does it crash overnight when you aren’t listening to anything?
Hi, thanks for responding.
Roon crashes when it is not playing anything. I just have it running so I can play music on my Linn systems. So it can’t be a case of being overstressed or something like that.
Maybe I can send yoU a logfile or something? I haven’t been able to find a log in the settings so you have to guide me to it. I can send you the MacOS crashlogif you wish. Tell me what you want me to do.
Thanks.
Willem
Same problem here. I’m running Roon on a MacBook Pro:
macOS 10.14.6 (18G87)
MacBook Pro (15-inch, 2017)
Processor 3.1 GHz Intel Core i7
Memory 16 GB 2133 MHz LPDDR3
Graphics Intel HD Graphics 630 1536 MB
Roon 1.7 (build 537)
Sometimes it will just stop at the end of a song and won’t play any more tracks, sometimes I can click on the back button and navigate around to get it to play again, sometimes I can reboot and it will work again for a while. Right now it’s acting as if there is no Internet connection. It will play music on my machine, but nothing else. Obviously I have an Internet connection since I’m writing this… 
Joel
Hello @Willem_Keller,
I have noticed similar issues in the past where your power settings can be a factor, especially if Roon is crashing overnight when the machine might be going to sleep. I recommend adjusting those power settings and see if you still get crashes.
If that’s not what’s going on then when it next crashes please reply here with a timestamp (your local time) and we can get some logs and see whats going on in the background. Let me know!
Hi. It crashed again, without anything playing. The exact time was *according to the MacOS crashlog):
2020-05-14 18:37:26.119 +0200
I have saved the crashlog so I can send you that if you want.
Willem
Core Machine (Operating system/System info/Roon build number)
Mac Pro 2012 “5,1”, MacOS 10.14.6 “Mojave”
Roon version 1.7 Build 537 stable
Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Ethernet; all devices on the same network
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
Endpoints:
Linn Klimax DS (living room)
Linn Majik DS (study)
Linn Sneaky DS (barn)
Description Of Issue
Seemingly every day I get a Roon hard crash. It happens even when nothing is being played on one of the endpoints.
Latest MacOS crashlog (excerpt):
MacOS Roon crashlog 2020-05-12
Process: Roon [5400]
Path: /Applications/Roon.app/Contents/MacOS/Roon
Identifier: com.roon.Roon
Version: 1.0
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Roon [5400]
User ID: 501
Date/Time: 2020-05-12 21:36:14.658 +0200
OS Version: Mac OS X 10.14.6 (18G4032)
Report Version: 12
Anonymous UUID: 6B46BD58-7774-6176-128B-9DAD4CAA9E14
Sleep/Wake UUID: 4DFC8FE9-2929-4515-A629-2FDF4BFBF812
Time Awake Since Boot: 2700000 seconds
Time Since Wake: 36 seconds
System Integrity Protection: enabled
Crashed Thread: 32
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
abort() called
Thread 0:: tid_307 Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff76af121a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff76af1768 mach_msg + 60
2 com.apple.CoreFoundation 0x00007fff4a9babdd __CFRunLoopServiceMachPort + 327
3 com.apple.CoreFoundation 0x00007fff4a9ba14a __CFRunLoopRun + 1619
4 com.apple.CoreFoundation 0x00007fff4a9b98a5 CFRunLoopRunSpecific + 459
5 com.apple.HIToolbox 0x00007fff49c0a1ab RunCurrentEventLoopInMode + 292
6 com.apple.HIToolbox 0x00007fff49c09ee5 ReceiveNextEventCommon + 603
7 com.apple.HIToolbox 0x00007fff49c09c76 _BlockUntilNextEventMatchingListInModeWithFilter + 64
8 com.apple.AppKit 0x00007fff47fa177d _DPSNextEvent + 1135
9 com.apple.AppKit 0x00007fff47fa046b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361
10 ??? 0x000000010fb4d702 0 + 4558477058
11 ??? 0x00000001168551c3 0 + 4672803267
12 ??? 0x00000001081d1c0b 0 + 4431092747
13 ??? 0x00000001081d1e31 0 + 4431093297
14 com.roon.Roon 0x00000001078a6d69 mono_jit_runtime_invoke + 1641
15 com.roon.Roon 0x00000001079e9b04 do_runtime_invoke + 84
16 com.roon.Roon 0x00000001079ed82c do_exec_main_checked + 156
17 com.roon.Roon 0x00000001077fc64d mono_jit_exec + 429
18 com.roon.Roon 0x00000001077ff7f8 mono_main + 9048
19 com.roon.Roon 0x00000001077b37d8 xamarin_main + 1144
20 com.roon.Roon 0x00000001077b4634 main + 36
21 libdyld.dylib 0x00007fff769bc3d5 start + 1
Thread 1:: SGen worker
0 libsystem_kernel.dylib 0x00007fff76af4866 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff76bb356e _pthread_cond_wait + 722
2 com.roon.Roon 0x0000000107ab00ee thread_func + 542
3 libsystem_pthread.dylib 0x00007fff76bb02eb _pthread_body + 126
4 libsystem_pthread.dylib 0x00007fff76bb3249 _pthread_start + 66
5 libsystem_pthread.dylib 0x00007fff76baf40d thread_start + 13
Thread 2:: Finalizer
0 libsystem_kernel.dylib 0x00007fff76af1256 semaphore_wait_trap + 10
1 com.roon.Roon 0x000000010796d30a finalizer_thread + 666
2 com.roon.Roon 0x0000000107a3f413 start_wrapper + 707
3 libsystem_pthread.dylib 0x00007fff76bb02eb _pthread_body + 126
4 libsystem_pthread.dylib 0x00007fff76bb3249 _pthread_start + 66
5 libsystem_pthread.dylib 0x00007fff76baf40d thread_start + 13
Thread 3:: tid_7103
0 libsystem_kernel.dylib 0x00007fff76af4866 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff76bb35a1 _pthread_cond_wait + 773
2 com.roon.Roon 0x0000000107ac33b4 mono_os_cond_timedwait + 84
3 com.roon.Roon 0x0000000107acf61d mono_thread_info_sleep + 429
4 com.roon.Roon 0x0000000107a37352 ves_icall_System_Threading_Thread_Sleep_internal + 98
5 com.roon.Roon 0x000000010798f602 ves_icall_System_Threading_Thread_Sleep_internal_raw + 66
6 ??? 0x000000010fe54c3d 0 + 4561652797
7 ??? 0x000000010fe53d9b 0 + 4561649051
8 com.roon.Roon 0x00000001078a6d69 mono_jit_runtime_invoke + 1641
9 com.roon.Roon 0x00000001079e9b04 do_runtime_invoke + 84
10 com.roon.Roon 0x00000001079ebb3b mono_runtime_delegate_try_invoke + 203
11 com.roon.Roon 0x0000000107a3f43e start_wrapper + 750
12 libsystem_pthread.dylib 0x00007fff76bb02eb _pthread_body + 126
13 libsystem_pthread.dylib 0x00007fff76bb3249 _pthread_start + 66
14 libsystem_pthread.dylib 0x00007fff76baf40d thread_start + 13
Thread 4:: Timer-Scheduler
0 libsystem_kernel.dylib 0x00007fff76af4866 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff76bb35a1 _pthread_cond_wait + 773
2 com.roon.Roon 0x0000000107ac33b4 mono_os_cond_timedwait + 84
3 com.roon.Roon 0x0000000107a5f009 mono_w32handle_timedwait_signal_handle + 201
4 com.roon.Roon 0x0000000107a5eed1 mono_w32handle_wait_one + 769
5 com.roon.Roon 0x0000000107a5f159 mono_w32handle_wait_multiple + 201
6 com.roon.Roon 0x0000000107a38e43 ves_icall_System_Threading_WaitHandle_Wait_internal + 163
7 com.roon.Roon 0x000000010798ff28 ves_icall_System_Threading_WaitHandle_Wait_internal_raw + 88
8 ??? 0x000000010fc9f9b6 0 + 4559862198
9 ??? 0x000000010fc9f5e3 0 + 4559861219
10 ??? 0x000000010fe549b8 0 + 4561652152
11 ??? 0x000000010fe53d9b 0 + 4561649051
12 com.roon.Roon 0x00000001078a6d69 mono_jit_runtime_invoke + 1641
13 com.roon.Roon 0x00000001079e9b04 do_runtime_invoke + 84
14 com.roon.Roon 0x00000001079ebb3b mono_runtime_delegate_try_invoke + 203
15 com.roon.Roon 0x0000000107a3f43e start_wrapper + 750
16 libsystem_pthread.dylib 0x00007fff76bb02eb _pthread_body + 126
17 libsystem_pthread.dylib 0x00007fff76bb3249 _pthread_start + 66
18 libsystem_pthread.dylib 0x00007fff76baf40d thread_start + 13
There is more info in the crashlog. Please let me know how I can email that to Support.
Thanks.
Willem
Netherlands
Hello @Willem_Keller, I’ve got something to test for you! Could you please follow the directions here to disable notifications when your screen is off.
One of my coworkers had this issue and we’ve had success with a few other users. Let me know if that helps!
Hi. I’ve looked at those setting, but they were already as suggested.
So that will not be the cause of the problem.
In the meantime, it crashed again. And again while playing nothing, so just running idle on my Mac Pro Core.
Maybe there is something wrong with energy settings? They are currently as follows:
As it is now, the Mac Pro monitor goes idle after 5 minutes and the whole computer goed to sleep after 15 minutes. Do I need to change this setting ? Let me know, please.
Willem
Well, it crashed again. 
I am no programmer, but I thought I might look art the MacOS crash logs to see what I could find. I have studied a number of crashlogs that I saved, and there is one thing that has drawn my attention. I don’t know if it is relevant, but there is always a certain type of program thread that crashes. This seems to be linked to OpenHome, whatever that may be.
This is an example:
Thread 32 Crashed:
0 libsystem_kernel.dylib 0x00007fff76af72c2 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff76bb2bf1 pthread_kill + 284
2 libsystem_c.dylib 0x00007fff76a61745 __abort + 144
3 libsystem_c.dylib 0x00007fff76a616b5 abort + 142
4 libohNet.dylib 0x0000000133aa7bc9 OsQuit + 9
5 libohNet.dylib 0x0000000133a34afa OpenHome::UnhandledExceptionHandler(OpenHome::Exception&) + 378
6 libohNet.dylib 0x0000000133a9c50b OpenHome:
:EntryPoint(void*) + 443
7 libohNet.dylib 0x0000000133aaa096 threadEntrypoint + 262
8 libsystem_pthread.dylib 0x00007fff76bb02eb _pthread_body + 126
9 libsystem_pthread.dylib 0x00007fff76bb3249 _pthread_start + 66
10 libsystem_pthread.dylib 0x00007fff76baf40d thread_start + 13
And another example from another crashlog:
Thread 37 Crashed:
0 libsystem_kernel.dylib 0x00007fff76af72c2 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff76bb2bf1 pthread_kill + 284
2 libsystem_c.dylib 0x00007fff76a61745 __abort + 144
3 libsystem_c.dylib 0x00007fff76a616b5 abort + 142
4 libohNet.dylib 0x0000000136e96bc9 OsQuit + 9
5 libohNet.dylib 0x0000000136e23afa OpenHome::UnhandledExceptionHandler(OpenHome::Exception&) + 378
6 libohNet.dylib 0x0000000136e8b50b OpenHome::EntryPoint(void*) + 443
7 libohNet.dylib 0x0000000136e99096 threadEntrypoint + 262
8 libsystem_pthread.dylib 0x00007fff76bb02eb _pthread_body + 126
9 libsystem_pthread.dylib 0x00007fff76bb3249 _pthread_start + 66
10 libsystem_pthread.dylib 0x00007fff76baf40d thread_start + 13
Does this mean anything? The thread number is not constant in the crashlogs that I saved, but the info is.
Let me know if you need anything to diagnose this further.
Willem
Hello @Willem_Keller and thanks for trying that! As I said previously, let’s get some logs over to my team for further review if the notification preferences weren’t the solution. Would you kindly use the directions found here and send us over a set of logs using this link. Please be sure to do this no the Mac Pro, thanks!
Let me know when you’ve uploaded the files and I’ll get them over to my team for further review.
Hi. Logfiles are uploaded.
Willem
Thanks, @Willem_Keller for the logs! I got this and the mac log crash data over to our team for further review. We’ll take a look and see what might be causing the crash. I’ll be in touch shortly!
Several days ago I changed my settings to be like that and I’m still having intermittent connectivity issues. The difficulty is that there seems to be no pattern to them. Sometimes music will stop playing and sometimes the next song just won’t start. Frequently I can push enough buttons that it somehow gets unstuck. I’ve checked my network monitor each time and Roon is still connecting to services outside. I didn’t have a bit of problem until a few weeks ago. Joel
No updates yet ???
Hello @Willem_Keller, thanks for your patience on this one. I spoke to our QA team about your issue today and they let me know that we have a ticket open with our development team to address this problem. I can’t provide any specific timelines just yet, but we’ll be sure to let you know when we have more information on this.
In the meantime, we recommend closing Roon when not in use. Thanks again for your patience here!
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
