I know that the support team is somewhat behind on answering tickets. From what I understand they have access to logs from your server, but you will need some patience to get an answer from them.
In the mean time I can only offer some advise on what I would check and try if I were in your shoes. Bear in mind the I’ve only been a Roon users for a few months and I’ve had the luck of (almost) everything running smoothly from the firs time.
In diagnosing an issue such as this, it is often a matter of trying to isolate potential issues. To get started, I have a few questions and a few things I would try:
What version and build of Roon are you running? You can check via Settings > About.
You have a number of different endpoints. Are you experiencing the crash regardless of the endpoint you are choosing? For example does the crash occur if only streaming to the system output?
You say that you have 0 tracks in your library. Does this mean that when navigating to My Library > Tracks, the list is empty? Or do you simply mean that you have no local files, but that you have added albums and tracks from Qobuz and/or Tidal to your library? In case your library is truly empty, perhaps you can try adding an album from Qobuz or Tidal to see if that plays.
I just came across the following ticket. Although it’s on a Mac with an Apple Silicon processor it does seem similar to what you are experiencing. Unfortunately there does not to be a solution at this time, but support does seem to be aware of it and is taking it up with priority.
I was reading through that thread an there does seem to be a workaround that may work for you. You mentioned having tried running Roon on different Macs. Perhaps you could use one of them to run a Roon server. From the other thread:
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.
so an interesting update…I bought a Mac mini m2 today and installed Roon Server …wow… Roon now works as I hoped …maybe Roon should update minimum requirements to run…
I played 2-3 endpoints for over 12 hours with flawless performance…
@Gary_Clayton1 probably best to create your own ticket in the support category so that the Roon support team can treat it separately from the issue of the OP. When doing so, be ensure the fill out the template with as much information on your setup as possible.
We’re going to mark your previous post as resolved if the M2 machine has resolved performance issues. We’ll investigate the cause of your original report, but it’s likely you encountered a rare but known issue triggered in certain Mac setups. We’re in the process of debugging. Some machines may see it more than others, depending on OS, other software, etc. Your previous Core was still within system requirements, but the M2 is an impressive upgrade from which Roon will benefit. Should you encounter any crashing going forward, please let us know in a new thread.
The original issue remains and additionally I am not able to run server locally. Simply put, I have no way to play my music and it’s been over a month since I’ve been able to do so. Please resolve the original issue and I’ll be happy.
We’re aware of the situation; I’m simply making clear that double-posting across multiple threads is unproductive, as the entire team is following your original thread elsewhere, and your setup differs from the original poster here.
Please be aware that maintaining two Community accounts for one user is against our forum guidelines, and ties knots it our efforts to assist you via this platform by conflating your post history. Please choose either @Gary_Clayton1 or @Gary_Clayton to use, for clarity’s sake.