Memory Leak Issue with Roon Server (ref#6TIEU4)

What’s happening?

· Something else

How can we help?

· None of the above

Other options

· Other

Describe the issue

Hello, I recently installed Roon Server (2.0 build 1455) on a fresh installed Windows 11 Pro (23H2). After a while I noticed that the process RoonAppliance.exe is using a lot of memory (Working set) and it's growing day after day. Currently it's using 14GB of RAM after few days of running! When I restart the Roon Server, the memory usage (Working set) is 630MB. My audio libray is not so big and I didn't change it recently: 5468 tracks, 734 albums, 686 artists. Qobuz is connected. I suspect a memory leak issue in the Roon Server? I let all the parameters by default in the settings, I didn't made specific changes. Can you help please because currently I'm obliged to restart the Roon Server every 2 weeks I would say. Thanks.

Describe your network setup

Unify Dream Machine Pro

I have noticed similar dramatic memory increases over time on my iMac. So it’s not just you.

@Michael_Loomis - the best course of action is always to open your own Support request and describe your setup in detail if you want help.

You may have a similar symptom, but not necessarily the same cause as the original poster - your system setup may be different, that’s why the general rule is to always first open your own request. Let the Support team merge threads if they find common causes.

1 Like

The memory increasing over time does not automatically mean memory leak. What makes you think that this is the case?

It IS clearly a memory leak.
I have been reporting this for many months.
My most recent support thread about this is here :-

https://community.roonlabs.com/t/excessive-memory-usage-and-performance-slowdown-in-roon-server-ref-0bvmrs

Hi @Loic,
We are currently working on some changes to address this. They should be released soon but I cannot give you an exact timeline. Thank you in advance for your continued patience!

Hello,

it seems that the issue is related to these options:

When it’s setup to Off, there is no more memory leak.

Br,
Loïc

Thanks for the additional info @Loic . Our next production release should contain some changes in this area, let’s circle back once it is out and let us know if you still notice this behavior after.

FWIW, I have had these options off for some time now, on two servers…

And I definitely still saw severe memory leaking, and CLR stack overflows, on both of them.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.