Roon Remote crashes on iMac and iPhone while trying to connect to Mac Mini M2 (ref#U23217)

Running MacMini M2 with v15, iMac running Ventura 13.7 and iPhone running 17.7. Significant reliability issues, instant crashes, with many reboots or inability to find the server. I’ve turned on and off local network for roon on the Mini. What else can we try try?

I not a Mac user but, from other posts on this forum, I believe that the Sequoia 15.0 update (re)set some firewall settings to a state that is incompatible with Roon. Do a search for “Sequoia”. E.g.

https://community.roonlabs.com/search?q=Sequoia%20order%3Alatest

I found this post:

1 Like

Hi Wade - Tried this. Not working for some reason. I can an instant crash report on the iMac and Mac Mini M2 server.

I can’t help you with iMac crash reports. I don’t use Apple devices of any kind.

F.Y.I. I am not employed by Roon. I am just an user of some 18 months standing.

In your first post it wasn’t clear that you are experiencing crashes. This is a different problem

I replaced a failed mini PC with a Mac Mini M2 running 15.0 a few days ago. No issues streaming to two different endpoints (Zen Stream, Linn Series 3), controlled by a Macbook (also on Sequoia) and a Pixel 8. Network: cable modem to UniFi UDM, wired directly to Mini and to endpoints via Netgear GS105 switches.

Is Roon Server running?

· Yes, Roon Server is turned on and running.

What do you see on your screen?

· I see something else

When you try to connect, what screen do you see?

· I see something else

Please try to restart your Roon Server by closing the Roon app in the taskbar or rebooting your Roon Server machine.

· No, the issue remains the same

Please try to restart your network setup by unplugging, waiting 30 seconds and then replugging in your networking gear.

· No, the issue remains the same

Please select how you've connected your Roon Server to the internet

· Roon Server is connected by *Ethernet*

Have you checked your firewall settings to ensure that Roon is allowed through?

· Roon still won't connect even after checking this aspect

Have you verified that Roon Server is on the same subnet as your Remotes?

· My Remotes and Server are on the same subnet and I still can't connect

Sometimes the issues can be resolved with a reinstall of your Roon Remote app. Let's try to perform a reinstall and see if it helps.

· I've reinstalled the Roon Remote but it did not help

What is the operating system of your Roon Server host machine?

· *MacOS*

Select any of the following components that are present in your local network setup

· None of the above

Describe the issue

Roon Core is a Mac Mini M2 v15.0 running Sequoia. Roon remote iMAC Ventura 13.7. Firewalls are off, M2 local network access switched on and off per some suggestions. iPhone or imac immediately crash - with report. Multiple reboots of everything does not resolve the issue (network, router, server, imac, phone). Roon us unusable at this point. Server and iMac wired, on the same network. Roon server appears to be running on MacMini M2 but Roon Remote on iMac or iPhone won't connect.

Describe your network setup

Wired Gig and Deco Wifi 6. Server and iMac are wired. Same network, no VPNs, no FW's enabled.

Hi @Chris_Lischy,

Some users have erroneously suggested that you deactivate the firewall on your MacOS machine; please don’t, as this exposes it to unwanted network traffic. We instead recommend that you add Roon’s processes as exceptions to the firewall.

On the iMac (not the Mac Mini), please use the instructions found here and send over a set of logs to our File Uploader.

Thank you!

Hi - Logs have been uploaded. Thanks - Chris

Hi @Chris_Lischy,
Based on what we found in your logs we have 2 things for you to try.

  1. Refresh the Roon app on your iMac with the below steps.

    • Create a Backup of your current
      database
    • Exit out of Roon
    • Navigate to your Roon 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
    • Verify if the issue persists on a fresh database before restoring the backup
  2. Try early access. This article will help walk you through that.

Please let us know the results of trying these options!

Daniel - This will be the second time I did this so we’ll see. It wasn’t stable for long. The early access link you provided doesn’t exist or I’m doing something wrong.

I’m not sure why the link failed but here is the information you need from the article

Updating Windows or macOS Roon Servers or remotes to earlyaccess

  1. Shut down Roon / RoonServer if either is currently running
  2. Download the appropriate installer package(s) for your platform using the links below
  3. Open the downloaded file(s) and execute the installation process as you would normally

This will install the earlyaccess version of Roon and/or RoonServer onto your computer. This is a completely non-destructive process and is no different than installing any Roon update.

You will need to repeat this process for any computers on which you use the Roon application as a remote to your server.

Thanks Daniel. I’ll give it a try

no good - after syncing the music and then attempting to change the theme from light to dark, roon on the imac crashed. iPhone attempts to open Roon and immediately closes and exits. After rebooting the iMac - roon say’s it’s waiting for the server which shows Roon running

Daniel - Do the logs provide any reason insight? I cannot use Roon even though the server shows Roon running. Both the remote iMac and iPhone crash or exit out. iMac provides a crash report -

I now have an issue loading the library from the imac. Roon server is running on the Mac Mini M2

Hey @Chris_Lischy,

Thanks for sharing the additional information. We were able to review a fresh diagnostic report from your Roon Sever, and saw traces of database-related corruption:

Critical: scx: LevelDb.Exception: Corruption: bad entry in block

This could be related to the crashing that’s been occurring - have you made a fresh backup recently? If so, you should be safe by restoring that backup.

If you could, please also upload a copy of the Apple crash report : File Uploader.

We’ll be on standby for your reply, thanks!

That error looks hard drive related. I already attempted to restore from a fresh back up off of the primary drive and Roon just crashes. I’m now making the backup drive the primary drive to see what happens. Will let you know.

Didn’t work. Roon just crashes. Mac Crash report uploaded. Also restored from a backup and that hasn’t worked. Changed source drive to backup drive but same issues.

Here’s what ChatGPT has to say about my crash – The crash you experienced was caused by a “segmentation fault” (EXC_BAD_ACCESS / SIGSEGV) in the Roon application. This occurs when the program attempts to access memory that it is not allowed to. Specifically, the crash occurred on thread 31, which was trying to handle string literals in the libcoreclr.dylib library, a core part of Roon’s underlying framework.

The issue appears to be related to an unsafe memory access while resolving string references or performing Just-In-Time (JIT) compilation for .NET code. The crash report repeatedly points to failures in the string literal management, indicating an attempt to access invalid memory.

This kind of error can be caused by various factors:

  1. Memory corruption or mismanagement in the app’s code.
  2. Incompatible or corrupted installation files, especially within the libcoreclr.dylib library or other related libraries.
  3. System resource limits, such as memory or processor load, that may cause instability in the app’s execution.

To resolve this, consider:

  • Reinstalling the application to ensure all libraries and dependencies are properly installed.
  • Updating the application, as the crash could be due to a bug in the current version that may have been fixed in later releases.
  • Monitoring system resources while running the app to ensure your machine has enough memory and processing power.

If the issue persists, reporting the crash log to Roon’s support might help identify the specific bug.