Hi, Running Roon as remote (control) on a 2017 i5 MacBook running Catalina 10.15.5.
Ever since the latest update (Roon’s) have the following issue: I leave home and also use the MacBook at work. If I don’t quit the Roon app, and it keeps looking for a core (obviously on a different network) 9-10 times my laptop is used at work, it freezes and restarts.
In the report generated from MacOS it is clear that the issue is with the Roon software. An obvious solution would be to quit the Roon app before I leave home, but I sometimes I forget, and anyhow I think this is a bug.
Hello @Dimitrios_Mimis, and thanks for this report! I’ve passed this information along to our QA and development staff, and after their review and comparison to other kernel panic reports we have seen in the past. Our staff has determined that Roon itself is not at fault for this behavior as this type of issue cannot be caused by an app as it is a system-level error.
We also ask that you review the contents of this article from Apple’s support team regarding instances of this issue. We recommend that you reach out to Apple support with this trace and see what they say!
Hi. Thanks for the answer. While I understand your point there are three issues. 1st, in the Apple support article you ask me to review, it specifies that these restarts are caused by either a particular software, or some hardware attached to the Mac. As no hardware is attached, it therefore must be software related. 2nd, on the report issued by the OS, when it crashes, it clearly states the following: BSD process name corresponding to current thread: Roon (and its the only software mentioned in this report). And 3rd, when Roon is not running (as mentioned before, on a different network) this unexpected restart has never happened (Ever). While point 1 is obviously a speculation, points 2 and 3 are facts. Especially point 2, where in the crash report it clearly states that the process Roon is what generates the panic codes. Please look into it some more. Thanks again for your time.
Nuwriy brought your question to my attention and I am hoping I can help clear some things up. We met with our QA lead and our CTO to discuss this issue last week and Nuwriy’s previous reply was based on their feedback.
While this error may be triggered by Roon, it is important to note that this type of error cannot be caused exclusively by Roon. Mac OS (and most modern operating systems) sandbox apps that are running, effectively meaning that the app can’t cause issues with the underlying system. Kernel panics are an error that happens at this underlying system level when low-level code on the OS level fails. Roon might be triggering something that exposes an underlying issue, but the issue itself isn’t from Roon, if that makes sense.
We haven’t been able to reproduce this error in-house, and we aren’t seeing widespread reports of this issue either, so it looks like something specific to the environment of your Core machine is doing something differently when Roon interacts with it, resulting in the kernel panic.
I’m sorry I don’t have better news for you here, Dimitrios, but I hope this helps to clarify what is occurring here. if you have any questions about the above please let us know!
I have the same issue, but I am not able to reproduce it
@ Dimitrios_Mimis
Do you see the following in the top of the .panic reports?
/Library/Logs/DiagnosticReports/
“bug_type”:“210”
Maybe it is related to the following?
My trace is more or less identical:
Kernel trap at type 14=page fault
Kernel Extensions in backtrace:
com.apple.iokit.IOAcceleratorFamily2(438.5.4)
and top dependency: com.apple.driver.AppleMobileFileIntegrity
BSD process name corresponding to current thread: Roon
I only have kernel panics since i installed roon (a week ago) 3 kernel panics till now, all stack traces contain the lines listed
@Sander_Puts HI. It hasn’t happened since initially posting this thread, but I now knowingly quit the Roon app on my MacBook when leaving home. (TBH I avoid using it all together and use an iPad or my iPhone for control). As stated, this issue presented itself ONLY when the MacBook was on a network different than the one the Core is on, AND the Roon app running. When at home, connected to the same network as the core, this does not occur. Underlying issue or not (with MacOS) this only happens when Roon is running (and away from core). Regarding the kernel panic bug you mention, its for Mojave, while I currently run Catalina and I was using Catalina with Roon prior to this. This started happening after the latest Roon update and not a MacOS update.
Hi, thanks for the additional info. Sorry for posting an irrelevant link, I run mac OS X 10.15.5 as well.Yesterday when the panic occurred I had indeed network issues and my core couldn’t be found when waking up the Mac from sleep. So far I am not able to reproduce the error, nor by unplugging network cables, nor by stopping the roon core. Maybe it requires the powernap to run. For now I will disable my Avast virusscanner, let’s see if that solves it. “Unfortunately” I am not experienced in debugging OSX panics
Mmmm just got a panic for the 4th time. Report looks different now, although the roon thread is still the trigger of the panic. After reboot my bluetooth devices did not work anymore. Had to reset NVRAM and SMC.
FWIW, I am getting panics with a very similar trace (2019 16" MacBook Pro). If helpful, let me know and I can paste the full trace. Needless to say, not a good thing when a laptop abruptly shuts down with a panic during a Zoom call.
Related to above experiences, I do not have Avast. I do have Carbon Black. I am running Roon as remote to a separate Roon server
