Roon isn't stable and they edit their forum to hide it

Equally, when you're the one who encounters a problem, it looks like it's a terrible coding job, whereas you may be running into some kind of platform-specific edge case. Unfortunately no software is completely free of bugs. I hate running into bugs, and I hope that the ones affecting you are fixed soon.

By the way, what platform are you using to run the Core?

Many of us use Roon for months and months without ever needing to restart the Core. In my case, running ROCK on a small dedicated PC (NUC), I think I've restarted (aside from updates) once or twice in three or four years.

Hmmm.

Their moderators edit and delete posts.  It can get a little Orwellian. 

@mike_in_nc I agree with you.  I've used Roon for 4 years with a cheap PC (NUC).  I've certainly had to restart it more than once or twice but I've never had any serious issues or problems that weren't resolved with a simple restart.  Asserting that Roon isn't stable in any general sense is almost certainly untrue, but that doesn't mean any given user's configuration might not be causing problems.  In my case I have an external hard drive that periodically needs to be attached to a PC in order to be "repaired".  I doubt that is an issue with Roon but I am sure some users might view it that way.  Given how insanely complicated Roon must be, and the amazing functionality it provides, I think it is understandable that the "moderators" are (overly?) zealous about censoring posts they might view as slanderous.

I have never used Roon.  That said, if this issue may be more configuration related than Roon service related, might that fact be an excellent discussion on Roon’s forum?  

I've been using Roon since 2017 and I have a lot of experience with it. I've built maybe 10 different Roon servers/cores, possibly more.  Some Windows 10/11, some Ubuntu.  I don't know MacOS well enough to try my hand at that.  

In the end, what I've done is build 2 cores and I can switch between them when one is running the process that effectively kills Roon.

I certainly understand that many people don't have the same issues.  My take on this, after a ton of experience and communications with other users having similar problems, is that it's a metadata/database update process.  It's not network or hardware configuration.  

Why does it only affect some people?  I suspect it has to do with library composition - use of Roon's tags, and unidentified albums could be culprits.  

The main issue with this instability is that Roon uses only one core for this process and it maxes out the core and makes Roon slow to unresponsive and it then ultimately restarts itself, which of course interrupts the music.  That restart doesn't reset Roon to functional - the problem continues until the process is done. 

Anyway, that's what I was referring to.

In terms of the forum, I've had posts edited to leave positive comments and remove negative...and lately just deleting negative posts. 

This is not to say I don't love the product.  Well, it's a love-frustration thing anyway.  But I haven't found anything better.  I just wish Roon would code away from this architecture that does this.