I launch the application and after I hit play for 10 min or so the application unexpectedly quits. This happens regardless of the playback device that I’m using.
Do you mean that Roon Remote crashes? Or does Roon stop functioning completely… music halts etc.?
You do have quite a large library. About ten times the number of tracks that I have. Are these all local or also from Tidal/Qobuz? If so, do you have a substantial amount of tracks from streaming services? Maybe you could try to logout from these services temporarily, just to try if Roon operates smoothly without?
No streaming. The Roon core just quits unexpectedly. Doesn’t have to be playing anything. It could just be open with nothing streaming or playing, and it still quit unexpectedly
Thanks for sharing that. Unfortunately, you’re experiencing a known issue with Mac devices that were currently working through. Here is the tracking thread:
It’s a high property for our team, and I’ll keep you updated with any new information as things progress. In the meantime, many have been able to navigate around the crashing by temporarily switching to running Roon Server on their Mac.
Roon server would replace your all-in-one application as your core. You can still operate Roon with the all-in-one instance though.
Steps:
Download and install Roon Server from my link here. Once Roon server is installed, you’ll see a Roon icon across your top menu. Click it and select the option to launch at startup.
Take a backup of your database and put it in a safe location.
Go to Roon>Settings>General and log out of your core. Select the newly created instance of a core (Roon server) and log in.
Restore your database.
This should work as a solid workaround and won’t require you to leave the Roon interface up for Roon to function.
We’re not able to speak on any specific timelines yet. The ticket is marked as a high priority though, and our team is actively working on it. I can certainly keep you in the loop with any new information as things progress.
If you do want to give Roon Server a try, certainly let me know and I can provide an easy step-by-step, just to try it out as a way to get you back to your music!
I don’t have much to report yet, unfortunately. This issue is still marked as a high priority and is in the development queue being worked on. I’m hoping to have more information to share soon.
Probably unrelated (except that it probably was an earlier crash that caused the lock file to be left behind without getting deleted). If the old lock file still exists and may have the wrong file permissions, the new one can’t be created. This helped other people but is a bit too heavy-handed:
… as @Nepherte correctly says in the subsequent post:
What should be done is to find the specific Roon lock file in /tmp and delete it specifically, or find the permission problem and correct it, not change ownership on the directory
Yeah, @benjamin can you look into this lock file problem as described above? I don’t have Roon Server running on the Mac and can’t try to see what the lock looks like.
We are actively investigating it further, but don’t have any new information to share yet, other than the workaround which is what you’ve shared above:
Open Terminal.app on your mac
Type the following commands and hit enter after each command:
cd /tmp
then sudo chown $(whoami) /tmp
You may be asked to enter your Mac password after that last command.
Thanks for the update. I’m not seeing any new devices from your account page - could you provide a bit more information around your process with the new computer? Did you migrate from your previous mac using Time Machine?
Did you suffer crashing from both using the all-in-one Roon download as well as Roon Server? On the new machine, do you receive the same crash report? Any additional details would be helpful. Thanks!