I think Roon crashing on the M1 chip is a similar issue to that raised by others, but I’m not sure the circumstances are the identical. I’m finding on both Mac mini’s I’m using, Roon tends to crash overnight. When I return most mornings, I either find part of Roon isn’t working (Roon not finding any output devices), or it has crashed. Seems to work fine the rest of the day
Hi @JeremyAH ,
Does a fresh Roon database + a small local library exhibit the same issue?
- Make a Backup of your current Roon Database
- Exit out of Roon
- Navigate to your Roon’s Database Location
- Find the folder that says “Roon”
- Rename the “Roon” folder to “Roon_old”
- Reinstall the Roon App from our Downloads Page to generate a new Roon folder
Unfortunately, this didn’t solve the problem. I had been running Roon Server on an Intel machine and the remote control running on the M1 would crash overnight.
I’ve now moved the Roon Server to a completely new machine by doing a backup on the previous server and restoring the database to the new one (another M1 Mac) and am now getting the same issue on both machines (although less frequently, I think, than I was before the latest release of Big Sur).
Interestingly, both the remote and Roon Server were running at 10.30pm this evening and I’ve just returned to them four hours later to find the remote has shut itself down and the server can no longer see the end points. I wonder if something unmagical happens when the day changes?
Our team is investigating some reports of macOS crashing when waking up from sleep. I don’t have any specific timeframes I can provide, but this is something we’re actively looking into and hope to resolve in the future. You have our apologies for the trouble!
I think there were bound to be some teething issues with the M1! Incidentally, the Mac running Roon Server isn’t set to sleep, so this may not be the issue with this machine.
I have this same issue on a 2019 Mac with the i5 Intel chip. I’m running the latest OS version. Roon also causes memory problems and slows my Mac to a crawl. Sometimes just quitting Roon will fix, but sometimes I have to hard shut down my Mac even after quitting Roon. Problem happens for certain if left on overnight.
I’m now running the public beta of macOS and it’s behaving a lot better. I’m not encouraging you to necessarily download the beta, but it looks like a solution is on the way
Returned after almost one year and the issue is still there. Mac goes to sleep with Roon running → you wake it up and it crashed
Hi @Taras_Dzedzey ,
What OSX version are you using?
Does the same issue occur on OSX Monterey for you?
Just to chime in to say I’m having the same issue too (now on MacOS 12.0.1 (21A559)).
Hi @JeremyAH ,
Thanks for the additional info. Do you have any set of steps that you can share that reproduces this issue reliably on your end? We are still looking into this, but have been unable to reproduce the issue at-will.
I think the only thing that seems to be consistent is that if I return to the Mac the following day, it’s likely to have shutdown Roon. I’m not sure whether this is related to suspend mode or some other time-related event. Simply putting the machine in suspend mode doesn’t terminate the app.
Sorry for the late reply. It recently stop crashing, and I didn’t do anything.
Happens again, can attach report which I get on crash if it helps
That might indicate more than one cause as I ran into Roon crashing as soon as I moved from an Intel iMac Pro to an M1 mini, almost a year before Monterey was released.
Things are better than they were, but I can pretty much guarantee Roon will shutdown overnight.
@Taras_Dzedzey - If you notice any pattern to the crashes or an action triggers it, please let us know, thanks!
I’ve just noticed that Roon can shutdown after my Mac mini goes into suspend mode, rather than just overnight (I tend to listen to music in the evenings, so it wasn’t clear that this was happening until now!).
It’s worth pointing out that I’m using Roon on this machine purely as a remote. The core sits on an Antipodes K50.
In my situation that has start to happen since I changed to my new macbook pro M1 MAX.
I have also just updated roon to 1.8 build 880 today and unfortunately it didn 't help.
Basically on Macbook M1, Monterey version 12.1 (just updated) . Play music with QOBUZ , TIDAL or even local files.
Leave it play for 1 - 2 hours, when come back the music won 't play anymore even toggled “LOOP”. Also Disabled roon radio didn 't help.
When come back roon will show errors skipped to all over the tracks, even local track it won 't play anything, If attempt to play some local track it won 't work anyore.
The only thing that I can do is to restart roon application. Once restart it will start to play music again.
This never happen with my old MAC intel with monterey before.
Also it seems that if I still using laptop do some work and not leave it to only play music, the issues will not happen in my case. The power plan is setup to HIGHPOWER and laptop is plugged to macsafe properly. So it doesn 't matter whether it connect power to wall or by battery itself.
What kind of information that you need to fix this one? Pls let me know.
This kind of not playing through roon I have, too. For me it is appearing whenever the Mac is going into some soft sleep-mode or so (a couple of minutes after activating screen-saver).
I not only have the issue with roon, but with ALL programs that are listening to network sockets. It seems that the M1 is disconnecting on the Hardware side, but doesn’t notice the Software. So the Software (roon for instance) doesn’t know the connection is already dropped. Not sure this is an issue with roon, or even can be fixed by roon…