I recently subscribed to Qobuz in Canada, but whenever I activate that service, a memory leak causes the system to become unusable after several hours or perhaps one day. After a while, the Roon process start growing in size and when it reaches 8 or 10 Gigabytes, it becomes unusable: the music keeps dropping for long periods.
Note that I have been using Tidal for several years without any problems. Someone suggested the problem might be due to on-the-fly audio analysis of Qobuz data, but I deactivated that analysis completely and no change resulted.
Here is a description of my system:
Roon version (both server and remote): version 2.0, build 1311
Roon Server setup:
running under Windows 10
Intel NUC, i5-7300U CPU
32 Gig of RAM
500 Gig SSD
2 Tera internal drive for music library
connected on 10/100 ethernet
Audio device: Roon Ready Devialet 220 PRO streamer/amplifier.
I searched the forum and found some people reporting similar problems, but apparently this only happened with older versions of Roon and was fixed with more recent ones.
There is no on the fly analysis of Qobuz that’s purely for local files added to your library when it’s working out the DR and waveforms.
How many favourite albums are there in Qobuz ? Or is it pretty empty. Adding in a new service will briefly consume resources as it adds then to your local database and retrieves all the metadata. But it does sound like something else is going awry if it’s consuming that much ram. How many tracks do you have in total?
I know: my response is more than late… I had failed to monitor this forum since then.
Anyway, I did conclude that Qobuz was indeed the cause the troubles with my Windows Roon server. And I temporarily interrupted my Qobuz subscription, until I can find the time to migrate my NUC OS to Ubuntu or ROCK.