Sorry it took me a while to get back to the Nucleus - original case was (ref#IVPGQN) .
The extension mentioned previously is disabled. It was enabled on the Mac mini and caused no issues, however.
Note, BTW, that on the mini it’s quite clear that RoonAppliance is leaking ports; it was slowing down over time, and checking its memory (limited to 8GB) it was consuming over 140K Mach ports! A typical process is < 1000, and when started RA is about 500.
Looking back through post history, this issue or related RAM consumption problems have been rather long-standing. I think the most expedient approach would be to request a compressed copy of your current RoonServer folder from either the Mac Mini or the Nucleus database (whichever you’re currently using). We’ll attempt to reproduce this issue on the same database in-house on the same hardware setup.
Please, at your convenience, navigate to your RoonServer’s Database Location, zip up the entire RoonServer folder itself, and upload to our Database uploader.
OK, everything is uploaded as requested (the server also crashed after 7 hours, so I restarted it and waited for it to be idle before collecting the info).
Note, BTW, that the app also leaks ports like crazy. After about 12 hours, here’s what it looks like. This is sorted by number of open ports…nothing else comes close (and it gets worse and worse over time). This isn’t RoonAppliance - this is just Roon, running on a MacBook Pro.
I’ve been checking the server every so often, and even after reinstalling the OS software as requested, the Roon software has been crashing every 12 hours or so:
Thanks for sending the database over, we’ve escalated your case to the team for further review and will let you know once we have more details to share. Thanks in advance for your patience as we look into this!
It looks like your thread accidentally closed, possibly without a resolution. Some time has passed since your initial report, can you please confirm - are you still seeing the same behavior on the current version of Roon, or have there been any improvements? Let us know when possible, thank you.
Yes, it closed without a resolution, after I sent you the logging you asked for.
Everything’s the same. The macOS version is eating handles like crazy, and has to be restarted every once in a while, and the Titan is having the same issues as before as well.
It looks like your Titan is currently inactive. Could you please enable it again and use it as your Core for a while? This will allow us to collect fresh diagnostic data following the OS reinstall.
It’s up and running now, and has finished reindexing.
I gave you the database - were you guys able to reproduce the problems with the playlist search? Anything turn up with the previous diagnostics, database, etc?
So, I don’t know if it has crashed at other times overnight, but checking it this morning, it has clearly crashed within the last 20 minutes, despite not being in use at all. See stats: