@connor Not really, but I admit I’ve basically stopped “casually” listening via Roon. I do use search, filtering and browsing recordings via composition entry a lot (which I /think/ lands you on a pre-filtered album view for that work by default as well where the filter is separate from the usual FTS input box).
In short this is what drew me to Roon! It’s one thing that Spotify has “all the tracks”, but as a classical music lover it’s all but useful without a proper exploration database and navigation.
I do notice that FTS (full text search) becomes very slow very quickly, but I’m happy it even exists I can monitor more extensively when I have another “research” session.
Oh, in possibly related news, I had an incident where the client app suddenly informed me of database corruption, which I could only resolve by actually restoring from a backup. You might be able to see when that was, but I wager it was about a month ago. I received the message spontaneously when I hadn’t really used Roon for a few days.
Thank you again for your patience. The team has fixed a vulnerability that could create an infinite loading state between Roon Remote and RoonServer. It’s possible this was a factor in the behavior and symptoms you’ve reported in the long and arduous history of this thread.
How are things performing on the most recent build? Are you seeing any of the same symptoms with any of the same frequency?
We have ongoing efforts to improve performance issues, so any updates will help with future fixes, as well.
I’ll give it some more intensive attention the coming week(s)!
Interesting. Just going in for a quick baseline measurement, I found the unit with notably increased CPU usage over prolonged periods of time, which was usually a sign of bad things when the memory usage had grown to reach the ceiling
Thank you for the update, and we’re glad to hear that the issue has remained dormant.
For everyone else still affected by the issues described in this thread, rest assured we’re not resting on any laurels in our efforts to improve performance. There are several active tracking threads where users are noting behavior that resembles some of the issues brought to our attention here. We’ve fixed the issue identified and reproduced per the information reported here, so this thread will now close.
If you’re experiencing ongoing issues, please search the forum for a (recently-active) open thread or create a new one per our intake template. Thank you again for your heroic efforts to assist and inform our developers and tech support team.
I can monitor more extensively when I have another “research” session.
