Excessive memory use after latest update (ref#KR9J5I) [Ticket In]

[Alan_Sparks]

@noris

Hi @Alan_Sparks ,

Thanks for the report. We were able to enable diagnostics mode for your account and what this did was upload the error log to our servers for review, so no need for you to manually send it over. Looking over the error logs, we did notice the memory spikes, but it doesn’t appear to have happened in the last two days, is this accurate from your point of view as well?

When the memory issue last occurred, it seemed to happen right after a Qobuz sync, I wonder if this could be related to Qobuz. Next time you experience this issue, can you try to temporarily disable Qobuz via Roon Settings → Services and see if the issue persists?

You may be on to something re: Qobuz syncs. I disabled Qobuz for a few days and had no growth, today I re-enabled Qobuz and the server process grew almost 7 GB.

Hope you can get diagnostics and fix this. Thanks.

[benjamin]

Hey @Alan_Sparks,

Thanks for the additional info! This will be helpful for our development team, who will be investigating your case in more detail this week.

We should have more information to share once they’ve had time to take a closer look. Thank you for your patience in the meantime!

[Alan_Sparks]

Referencing Excessive memory use after latest update (ref#KR9J5I) [Ticket In]

Am still seeing the huge ballooning of the memory use of Roon Server after some time of operation. This with the current Server release on QNAP QTS 5.2.4.

I have the logs downloaded, if you want them advise where to upload them. Thanks.

[Michael_Harris]

Same here on DietPi, Roon has pretty much crashed twice after consuming 14GB of memory (used to be 6 to 8). I have gone back to a daily restart of the service now and just resterted it a few minutes ago manually.

This is what memory looked like until the restart

[Fernando_Pereira]

Ubuntu Server 24.04.2, 34k tracks. There might be a bit of a memory leak, or it could be just paging in of track details as more tracks are played over time. In any case, no trouble for a 32GB i7-13700.

[Alan_Sparks]

For me, the memory is leaking even though I’ve not had opportunity to play anything lately. Appears it’s whatever idle tasks the server is running, maybe Qobuz updates or something else.

[Michael_Harris]

I don’t have a Qobuz or Tidal library, but I do have a small Tidal listen later section.

I set my server to restart the Room app this morning at 6:30 and now at 9:00 it is sitting at a pretty low 4GB.
I have disabled all the Chromecast displays and Chromecast audio devices, remembering that there was supposed to be a fix for a memory leak in Chromecast (I rarely use them so it will be a good test)

[vadim]

Hello everyone,

Thank you for the update.

Our R&D team has identified and resolved the issue affecting Chromecast devices in the current release. We are now collecting additional diagnostic data from all impacted users to help R&D investigate and address any potential memory leaks.

Further general improvements are expected to be included in the next build.
Please let us know if the issue persists after the upcoming update.

[vadim]

Hello everyone,

The latest EA build delivered contains the fixes for the memory leaks. In case you are interested in testing, please feel free to install and test.

Please make sure to create a database backup before processing.

[Neil_Carpenter]

What was the cause of the memory leak that was addressed?