I just installed 2.56 (Build 1582) on Mac OS 26.0.1.
If I have a track playing and click an upcoming album icon in the Queue to inspect it, it crashes the Roon App running on the Mac (though the music continues to play). I did notice that this only happens on the same Mac that’s also running the Roon Server. The Roon app crashes, but the Server continues playing the track. Other Roon Remote apps running on other Macs on the network do not experience the crash.
Oh also, it still hasn’t fixed the nagging problem of finding other Roon-ready devices on the network after a reboot, without needing to go into Mac OS Settings → Privacy & Security → Local Network → and toggling Roon and Roon Server Off & On.
Describe your network setup
Direct Ethernet to Netgear ORBI Router (1G AT&T Fiber)
Before I try… are there any other things I might break doing this? I.e., will all of my music Library, Settings, Preferences, et al, be preserved or will I be starting from scratch?
Good question — yes, the steps above will temporarily reset your local Roon database, so your library, settings, and preferences will appear as if you’re starting from scratch.
However, nothing is deleted. The original database is preserved in the “Roon_old” folder, and you can restore everything at any time by simply closing Roon, renaming “Roon_old” back to “Roon”, and reopening the app.
This is just a temporary measure to test whether the crash still occurs on a clean database.
Apparently, this isn’t just happening on Macs. I’m experiencing the same behavior on all my Windows PCs. If I click on an entry in the queue or history, Roon crashes immediately.
Performing a Roon_Old won’t touch anything related to your Roon Server - so your library and settings are completely safe. Apologies for any confusion there, let us know if you run into the same issue on a fresh instance of Roon (not Roon Server.)
Thanks for confirming. We have had a few other reports of this issue, and the team is aware and working on this. I can’t specifiy an exact timeline, but we are hoping to resolve this crash as soon as possible.
Since there is nothing else needed on your end and we are able to reproduce this issue, I’ll go ahead and mark this thread for closure. Thank you for your patience as work is underway to resolve this!
The recent update didn’t include a fix for this new issue - sorry if there was any confusion there!
Since our team was able to reproduce the issue internally and we already have a ticket open with our development team to address it, there aren’t any next steps needed from you at this time. Because of that, we’ll go ahead and close this thread. You can expect a fix to be included in the next update or so - and of course, will be included in our software release notes that you can access here:
