GBit ethernet, various NETGEAR switches.
Music is stored on a NAS accessed over SAMBA.
Connected Audio Devices
Roon nodes: Roopieee (gb ethernet), Windows (gb ethernet), Android Phone (wifi).
Local audio: USB SMSL SU-9 DAC.
Video: HDMI, not used for audio.
Number of Tracks in Library
5,000 tracks
Also Qobuz.
Description of Issue
Roon version 2.0 build 1272.
When running, RoonAppliance uses 10GByte RAM (30GByte of virtual RAM), and about half a core of CPU. When connecting with Android or playing on remote nodes the connection frequently drops out for a few minutes. When the windows client is open I frequently see “waiting for roon core” pop up when nothing is playing. I guess the mean time between failure when playing on a roon node is 2-3 tracks, i.e. essentially unusable.
Nothing else running on the machine suffers from networking issues, nothing else has problems connecting to the NAS, or using the audio.
(just another Ubuntu 22.04.2 user) There have been a few reports of similar memory leak & slowdown problems, but it’s not a general problem on this platform. I have 30k tracks on an internal SSD, Roon Server is using 26.6G virtual, 798M real, snappy response.
Apologies for the slow response here. I noticed that you have since switched your Roon Core over to a Windows 11 PC, are you still seeing issues there or were the issues limited to the Ubuntu install?
It was just the Linux install that had problems (although there are a few minor niggles on Windows).
I switched to my desktop because the Linux server install was unusable, but I would prefer to use the Linux box because that machine is always on anyway and is only used as a media server.
Although now I’ve been using it for a while, it seems to crash on windows every couple of days, but only when I’m using it. This is a recent problem, as it’s been pretty stable up until now.
I’m using roon server on my desktop (because it wasn’t stable on my linux media server - see op).
Roon usually runs maximised, but I would have been switching from either my work vnc running fullscreen or Teams video running maximised to Roon.
In this case I switched because I could see my (passively cooled) PC getting quite hot, and I noticed that roon was using a lot of CPU. Clicking on the UI had no effect, I did manage to move the window so presumably some messages were getting through, but after that nothing so I killed it.
My professional opinion ( ahem … ) is that 7+ GBytes is a lot for a garbage collected user app, and 60% of a 6 core cpu is a bit OTT for an app that shouldn’t be doing very much minute to minute, so I expect this is some kind of bug even if the UI wasn’t completely dead .
Thanks for sharing the crash snippet, I’ll forward this to the team. Can you please access your old Ubuntu Roon logs using these instructions, upload the contents of the folder to the below link and let me know once uploaded? Thanks!