I didn’t know you had this history. Thanks for sharing it I’ve had my share of issues, too, including database corruption which had been included in backups for weeks.
I’ve run Roon on a variety of linux distros, on Rock, as a Synology app, and in a container. A few years ago, I wrote this walkthrough on how to stand up a container on Synology (prior to them supporting compose files) just about 4 years ago: Walkthrough : Roon in a Docker container on Synology DSM 7. I’ve been running Roon in a container since before I wrote that. It’s been the most manageable, predictable, and stable runtime environment for me.
Something changed in May. It might have been a change to Roon code, an updated dependency. or a configuration change. Or a combination of multiple things that are interacting in an unexpected way.
What frustrates me about this isn’t the regression, it’s my perceived lack of accountability and customer engagement on issues. Bugs come and go - people make mistakes, the combinatorial complexity of code, config, dependencies is hard to manage. It’s the sense that there’s nobody that actually notices or cares that’s the problem. The issues that a number of us have been discussing since May should be causing alarms on Roon’s dashboards, not just mine, to be firing.
In any case, I hope they do find and fix this. There seems to be some indication that they’ve found something.