Roon Still Bogging Down EVERY SINGLE DAY after five years

At one time I was a strong proponent of Roon. I figured the chronic instability was related to my Ethernet LAN or ISP. After five years of daily frustration, I no longer believe that. I’ve reconfigured the LAN, played with settings and even replaced my main gateway/modem but I still reboot Roon AT LEAST once per day. Possibly the worst software I’ve ever used.

1 Like

It does look like Roon may have a memory leak (see Excessive memory use after latest update (ref#KR9J5I) [Ticket In] - Support - Roon Labs Community) - my server usage has grown to over 14GB with a library of less than 10K tracks - time to restart again. If your server has insufficient RAM that would possibly explain your slowdown

Few details would help for starters

  • PC/server specification?
  • What OS , the link above refers to Linux
  • How much RAM - must be enough for library size
  • What processor - not a weak Celeron ?
  • How many Tracks (thousands of tracks)
  • are you connecting end points on Ethernet - Wi fi can cause this reaction
  • Anything else running on server PC?

Memory leaks are reported but most users don’t suffer , it’s probably something local

PS I shut down every night for climatic reasons (lightening in summer), I never see an issue . Is a routine daily restart such a chore ?

Switch on - brew coffeee - start listening :smiling_face_with_horns:

Hi @Paul_Pearah,

Clearly something is amiss as what you are experiencing is not normal behaviour from Roon.
I had a quick peek at your posting history to see what advice Roon’s support team had offered. However, it looks like your last support request was way back in July 2021 for an unrelated problem.

You’ve take the time to leave feedback Roon, may I also suggest you seek assistance from Roon technical support.

To equip the Roon Technical Support team to assist you directly, please follow this link to provide the details of your case to Technical Support: Technical Support Request

Respond to the prompts there to ensure that you’ve performed basic troubleshooting and to ensure Technical Support has the full details necessary to expedite Technical Support’s investigation into the case.

Your responses will auto-generate a Community thread in the appropriate section.

I hope Roon are able to get to root cause of these frustrating issues for you.

PS Rather than reply to @Mike_O_Neill here (Feedback topics are not the right place for technical support) but do please make sure to include the details in your support request doing so will really help Roon (and others from the community to help you).

1 Like

I’m using the GMKTec NUCBox G5 N97 mini pc as a Roon Core and it runs flawless.

1 Like

I had this problem and mucked around with Ethernet etc, similar to what you have done. I found it extraordinarily frustrating.

I stumbled across some posts on this site about RAM memory. My Roon Server (a Windows 10 machine i5) had 8 Gb of RAM. Using task manager, I was able to see that my usage of Roon was eating up RAM, it was going over 90% and continuing to climb. I upgraded to 16 Gb of RAM (which I got a computer shop to do at a very reasonable price). The problem almost, but not entirely disappeared, with rebooting Roon on the occasions that it did happen.

I have since changed my Roon Server to a mini Windows PC. I did this in anticipation of ending of support for Windows 10. It has 16 Gb of RAM but it is a more powerful i7 machine. It has been several months now since I have experienced any problems with Roon. I think that Roon is at fault by providing minimum specifications that are actually inadequate to the task at hand for many of its users.

The specifications state:

You will need sufficient RAM for Roon as well as any other tasks the machine may perform. We recommend 8GB as a minimum for Roon in addition to the base RAM for the machine. For Linux, Windows, and macOS this will typically result in a system with 16GB RAM or more.

I joined Roon in 2017! I am pretty sure then, they recommended 8Gb RAM. I am glad to see that they have updated this!