A number of people have suffered similar issues after installing an update, if you haven’t already, reboot your updated devices, core, iMac etc. it may resolve the problems and save a lot of time.
Oh well, it was a temporary fix. Roon again either refuses to open (beachball icon keeps on spinning) or crashes. Can Support please regard this problem as still needing a solution?
Thank you for reaching out to let us know about the persistent crash on your Mac Remote. I’d first recommend setting aside the database and trying a fresh install of Roon. While it may resolve the issue entirely, it will primarily create stable conditions for further troubleshooting steps.
Reinstall the Roon App from our Downloads Page to generate a new Roon folder
Verify if the issue persists on a fresh database before restoring the backup
Restore backup after fresh database testing
Please let us know if you’re able to launch the Roon client on your iMac successfully afterwards, and we’ll proceed from there.
@Matthew_Talbot, I appreciate you taking the time to upload logs. The tech support team will take a deeper look and circle back with next steps. I recommend you also try a database refresh per the above steps in the meantime.
I’ve split a few posts off from this thread for housekeeping, but rest assured we’re still attending to your original issue since it has persisted so far.
Did the database refresh in my previous post help at all? We’re standing by to support further if not.
Did all that. Yesterday Roon client (on iMac M1) would crash two or three times while attempting to open but finally opened (I tried this five or six times during the day). Today, no problems in opening it but I guess I’ll just have to test this over the next few days.
Unfortunately it’s doing the same thing again. A couple of times Roon has opened on the third try. Other times it crashes or freezes. I thought it might have to do with whether the streamer (Cambridge Evo 150 or Matrix Element-i and headphones) was switched off or on but that proved irrelevant and the behaviour seems to be random.
I appreciate you reporting in to let us know. The tech team is going to take a deeper look at the logs in this case to help us pin this down. I’ll follow up shortly once we’ve reviewed.