Roon server crashes after returning from sleep mode

Support
1

Core Machine (Operating system/System info/Roon build number)

MacBook 6.1
Mac OS X 10.11.6
Roon 1.7 - build 610

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)

ZTE H369A - DSL Modem/Router
Server connected by Ethernet

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

Raspberry PI + DigiOne Signature + Coax
Wifi connection to server

Description Of Issue

Everytime the MacBook, running the server, returns from sleep mode, the Roon server crashes. Problem started about a month ago. Before the exact same configuration was running excellent and returning from sleep mode. Except for crashes everything still runs smooth.

The (top of) problem details shown by Mac OS X:

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

Date/Time: 2020-08-28 23:42:17.316 +0200
OS Version: Mac OS X 10.11.6 (15G22010)
Report Version: 11
Anonymous UUID: 36A8EDF7-1047-1459-75CC-9DE3A72E8CF0

Sleep/Wake UUID: EF6ACA91-BDC4-4056-AC11-989AACA182CB

Time Awake Since Boot: 61000 seconds
Time Since Wake: 33 seconds

System Integrity Protection: enabled

Crashed Thread: 9 Broker:Transport

Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

VM Regions Near 0:
–>
__TEXT 000000010ffcd000-0000000110562000 [ 5716K] r-x/r-x SM=COW /Applications/Roon.app/Contents/MacOS/Roon

Application Specific Information:
abort() called
terminating with uncaught exception of type OpenHome::AssertionFailed

Thread 0:: tid_160b Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff9394ef72 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff9394e3b3 mach_msg + 55
2 com.apple.CoreFoundation 0x00007fff9a063114 __CFRunLoopServiceMachPort + 212
3 com.apple.CoreFoundation 0x00007fff9a0625dc __CFRunLoopRun + 1356
4 com.apple.CoreFoundation 0x00007fff9a061e28 CFRunLoopRunSpecific + 296
5 com.apple.HIToolbox 0x00007fff9bec9935 RunCurrentEventLoopInMode + 235
6 com.apple.HIToolbox 0x00007fff9bec976f ReceiveNextEventCommon + 432
7 com.apple.HIToolbox 0x00007fff9bec95af _BlockUntilNextEventMatchingListInModeWithFilter + 71
8 com.apple.AppKit 0x00007fff8ca40df6 _DPSNextEvent + 1067
9 com.apple.AppKit 0x00007fff8ca40226 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454
10 ??? 0x0000000119abbf3a 0 + 4725653306
11 ??? 0x000000012298bed3 0 + 4875402963
12 ??? 0x00000001122a206b 0 + 4599717995
13 ??? 0x00000001122a2291 0 + 4599718545
14 com.roon.Roon 0x00000001100fc2a2 mono_jit_runtime_invoke + 2354
15 com.roon.Roon 0x00000001102310f7 mono_runtime_invoke_checked + 135
16 com.roon.Roon 0x00000001102395be do_exec_main_checked + 94
17 com.roon.Roon 0x00000001100516ae mono_jit_exec + 414
18 com.roon.Roon 0x0000000110054985 mono_main + 9333
19 com.roon.Roon 0x0000000110008c6c xamarin_main + 1116
20 com.roon.Roon 0x0000000110009ab4 main + 36
21 libdyld.dylib 0x00007fff923945ad start + 1

3

Hello @Woody, and my apologies for the delay here. I wanted to take some time and run this trace by our team. We’re going to submit a ticket on your behalf to our QA team for further analysis. I’m going to enable diagnostics for your account now so we can create the report and I’ll return shortly with their feedback.

4

Thanks for the response and taken actions!
The issue still exists, so it should be visible in the traces.

5

Hi @Woody! Apologies for the delayed response from the long weekend.

I just wanted to confirm that the diagnostics report came in and the QA team is looking into the report. We’ll be sure to reach out ASAP once we have feedback from them. We greatly appreciate the patience as we continue to investigate!

7

@dylan Already any updates?

8

Hello @Woody, thanks for your patience while I discussed your report with the team!

Our QA team is currently investigating this and similar reports. We can’t provide any specific timelines just yet, but we’ll be sure to follow up as soon as we have more information.

9

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