Mac Mini (late 2012) 2.5Ghz i5 OS 10.15.7 Catalina, 16 GB RAM
Networking Gear & Setup Details
Ethernet through an unmanaged network switch connected to Airport Extreme Router
Connected Audio Devices
This is a Core only machine. It runs with no other purpose than to be a Roon Core machine. There are no audio devices connected to it directly. The music files are connected to an external USB hard drive. All audio devices are network connected. BlueSound Devices, Sonos Connect, AudioQuest Dragonfly Red via iMac as a desktop music system.
Number of Tracks in Library
21,980 Tracks
Description of Issue
Roon Core randomly quits. Never while in use. I’ll notice it every now and then when I’ll want to put music on and get the “No Core Found” remote screen. I then need to go to my main iMac to screen share with the Mac Mini and restart Roon. There is usually a Report option, but I haven’t screen-grabbed it as of yet. I noticed this starting to happen after the release of Roon 1.8. I’ve tolerated this up until now, given it not being that big a deal. But I would like to get it resolved if possible.
Ben with the support team here - sorry for the delay in getting to your thread. It’s good to see you on community again!
I was able to review a core diagnostic scan, and while I did see a few network-based errors, I wasn’t able to find anything specifically pointing toward unwanted crashes from your Mac mini.
When this crash occurs, do you receive any sort of crash report from Apple? Do you have any sleep settings tied to the Mac Mini?
As a good next step, if you could please take note of the date and time the next time this happens, an share that information here that would be helpful.
Thanks for following up. I have all sleep functions turned off. I do see Apple Crash Report options that I’ve ignored but won’t any longer. Next time it happens, and it will, I’ll provide the time stamp and any additional information.
Hi Ben,
Roon crashed several days ago, just before I was leaving town for a vacation. I received an Apple crash report which includes the date and time. I copied the report and can send it if that would be helpful. The date and time were 2023-08-09 16:56:33.650 -0700. Please let me know the next steps.
When I had my core on MacOS some time ago I had this issue as well. It looked like a memory leak issue. It would grow to a certain point, maybe 8 or 10gb+ and crash. This was one of the reasons why I moved the core to Windows. Haven’t experienced a memory leak on on Windows 11.
Thanks for sending that over! Our team is investigating things further, and agree that it would also be helpful to get a copy of your Mac mini console logs with a recent console crash report included as well (after a Roon crash takes place.)
I uploaded a Consol Log Report but I’m a bit confused as to what “crash report” I should send. Most of the crash reports are labeled WindowServer. I went ahead and uploaded the most current one.
Thanks for sending those over! In the meantime, while we further review things, lets double check to see if the crashing happens on a fresh database. Steps to follow are below:
Hi Ben, I’ve had the new roon database running since Sept 12th, and so far, no crash has occurred. It’s hard to say if I’ve given it enough time, as it happens randomly. It seems, however, I would have experienced a crash by now. Thoughts?
Thanks for the follow-up! Based on your testing so far, it seems the crashing is related to your prior database.
Do you by chance have another backup available that pre-dates this issue?
It may be fruitful to take a closer look at your prior database as well. If you could please locate this backup, zip it up (right-click it and select “Compress…”) and submit the .zip file to us through our Database Corruption Issues portal that would be helpful.
Hold up! It just crashed last night with the new database. So, maybe it’s not a corrupted database. I’ve used the link and uploaded a new crash report dated 9-21-23. Standing by. Cheers! Devin
Thanks for letting me know and sending over the crash report! I was able to review your Mac core, as well as remote logs around the specific time of the crash and see some interesting UI-related warnings right before the crash - I believe you may be correct in that it isn’t database-related.
With that, I see that your server (core) isn’t crashing during this - it appears to be running normally at this time. It is specifically related to your iMac remote. Do you have any specific display settings enabled on the device?
Or, do you have the display settings set to something unique? If you could share a screenshot of your display settings, that would be helpful!
This is really interesting. I’m experiencing issues with Zoom meetings freezing my computer when sharing my screen in meetings. I’m also experiencing a strange issue with Adobe Lightroom when using the Graphic Accelerator feature enabled. No one at Zoom or Adobe has a solution and it doesn’t seem to be a common issue amongst other users out there. This makes me think if I were to figure it out, it may solve a lot of problems. At least that’s the hope.
Nonetheless, I’ve uploaded several screenshots of my display, and energy settings. I look forward to hearing your thoughts.
@Devin_Dahlgren, your Mac mini is 9 years old and some of the apps you are using may have been updated and optimized for newer Macs and MacOS. Can you update to MacOS 12 Monterey (the most recent MacOS supported on your mini)? Apple typically applies OS optimizations and updates which may resolve what you are experiencing.
Based on the screenshots you’ve shared, do you have two additional monitors linked to your iMac? If you temporarily disconnect them does the issue persist?
If you test the above with only the primary monitor, and the crash still does occur, can you share another timestamp of the date, time, and track playing when the crash occurs?
