Hi @Griffin_Caprio,
Thanks for reaching out to us about this issue. I think the next step here is to enable some diagnostics on your account so our technical staff can get some more insight into what’s going on here.
However, before I enable this feature, I’d like to ask for your help ensuring we gather the right information.
First, can you please reproduce the issue once more and note the time at which the error occurs. Then respond here with that time, and I’ll make sure we review the diagnostics related to that timestamp.
Sure: I actually just opened Roon on my Mac for playback after having rebooted my Mac mini server. Even without playing a track, so Roon is just sitting open, it crashes. This is roughly 10:30 am CST
fyi @Daniel It’s still happening. I have a macOS Console Log Capture from the latest crash. I can send it over it it would help. If there’s other logging I can enable let me know, it’s pretty consistent and crashes ~4 mins after startup.
Hi @Griffin_Caprio,
Thanks for the timestamps and the extra details. I’m not seeing any crashes recorded in your logs. Were the crashes recorded in the Console app on your Mac? What do you see when the crashes happen?
I do see a lot of errors in your logs around certain albums. It looks like an issue with various artists that we’ve been tracking with a number of users. A fix for that got released to early access today.
Yes, the Roon application crashes and quits silently in the UI (there’s no error dialog or anything) and I see quit messages in the console log. For example:
default 09:26:27.839162-0600 audioaccessoryd AudioStateChanged: Received audioState Stop apps {
"com.roon.Roon" : 301,
}
default 09:26:27.832299-0600 runningboardd [app<application.com.roon.Roon.284316868.362768539(501)>:1763] termination reported by launchd (0, 0, 0)
default 09:26:27.958560-0600 runningboardd Removing process: [app<application.com.roon.Roon.284316868.362768539(501)>:1763]
default 09:26:27.959984-0600 runningboardd Removing launch job for: [app<application.com.roon.Roon.284316868.362768539(501)>:1763]
default 09:26:27.960705-0600 runningboardd Removed job for [app<application.com.roon.Roon.284316868.362768539(501)>:1763]
default 09:26:27.960743-0600 runningboardd Removing assertions for terminated process: [app<application.com.roon.Roon.284316868.362768539(501)>:1763]
default 09:26:27.960920-0600 runningboardd Removed last relative-start-date-defining assertion for process app<application.com.roon.Roon.284316868.362768539(501)>
error 09:26:28.015275-0600 runningboardd RBSStateCapture remove item called for untracked item 394-376-54816 (target:[app<application.com.roon.Roon.284316868.362768539(501)>:1763])
default 09:26:28.015404-0600 runningboardd Calculated state for app<application.com.roon.Roon.284316868.362768539(501)>: none (role: None) (endowments: (null))
default 09:26:27.864113-0600 audiomxd -MXSessionManager- -[MXSessionManager updateCanBeNowPlaying:didRegister:]: CanBeNowPlayingApp changed to NO for bundleID = com.roon.Roon
default 09:26:28.016590-0600 runningboardd Calculated state for app<application.com.roon.Roon.284316868.362768539(501)>: none (role: None) (endowments: (null))
default 09:26:28.237328-0600 launchservicesd Hit the server for a process handle 11bc6048000006e3 that resolved to: [app<application.com.roon.Roon.284316868.362768539(501)>:1763]
default 09:26:28.241405-0600 gamepolicyd Received state update for 1763 (app<application.com.roon.Roon.284316868.362768539(501)>, none-NotVisible
default 09:26:28.268922-0600 loginwindow -[PersistentAppsSupport applicationQuit:] | for app:Roon, _appTrackingState = 2
default 09:26:28.268939-0600 loginwindow -[PersistentAppsSupport applicationQuit:] | App: Roon, quit, updating active tracking timer
Can I get in on the early access somehow and see if that solves the issue? It’s been almost a week since this started and Roon is completely unusable.
Hi @Griffin_Caprio,
Thanks you for sharing the Console output. If these crashes keep occurring after trying early access I will open a ticket for you with our development team.
If you’d like to move your RoonServer machine and Roon controllers to the Early Access branch to try it out, you can follow the instructions here:
Please let us know if that make Roon usable again.
Hi @daniel unfortunately it didn’t fix anything. I upgraded to the EAP on both my server as well as macOS and playback still crashes on macOS. I’m happy to share any logs I can with the team but really need to get this figured out.
Roon ARC on iOS continues to work find as far as I can see.
quick update: I tried the Roon client on the same mac I’m using as my Roon server and it works fine. Same Roon library and everything. So it’s definitely a machine issue, but some differences:
Works on Intel Mac mini on Monterey 12.7.6
Doesn’t work on Apple M1 MacBook Pro Sonoma 14.7.1
So something has to be conflicting with it somehow, I’m just not sure how to debug further.
Hey @Daniel just a bump here to see if I can get some more help, either logging or something, from the team. I’m sure everyone is about to head out on holiday but I’d really like to be out of commission until '25.
Thank you for your patience. The team will be online through the end of the year with the exception of Dec. 24-26, so we won’t abandon this topic thread.
Here’s what we’ll need to escalate.
A set of logs from the Roon folder on the affected 14.x Sonoma M1 Roon controller (laptop). You can use the directions found here and send over a set of logs to our File Uploader?
Is Roon saved to the application folder on this machine, or are you running it from another location?
@Connor Great thank you. Logs updated from today. Confirmed crashes still happen.
It runs from the Applications folder
Yes, same machine but that issue turned out to be a bug in another audio utility, SoundSource. Sadly, I’ve tried disabling and uninstalled that as well and the crashing still happens.
hey @Connor and @Daniel just a note that this is still happening. I actually tried and removed all music from my Roon library (including Tidal and local files) and it’s still crashing. I really hope there’s something you can see in the logs because my only other option is to reinstall macOS which is definitely not ideal
ok, I was able to get this fixed by completely reinstalling macOS unfortunately. Wish I heard back from the team on some other possible fixes but it’s been over two weeks since the last note. Will follow up if there’s any more issues.