Roon experiencing memory leak (ref#NOYDO2)

Daniel -

Done.

Dave

Thanks for the quick response. I will review the results with the rest of the team and let you know when we know more.

Memory usage is increasing much faster, possibly because I am using it. Went from ~1 GB to 4.58 GB in less than an hour.

Hi @David_Moor,

We appreciate your patience while the team continues to hone in on a potential cause. As a next step in troubleshooting, please reboot your Roon Server twice, and see if you’re able to reproduce the issue.

We’ve enabled a debug tool with your Roon Server that will give us more insight into the issue area.

We’ll be monitoring for your follow-up :pray:

I suspect it might be helpful to the Roon support team if you could enable all of the memory-related columns you see in the screenshot below:

When you say reboot the Roon serve do you mean quit and restart Roon? The Roon process goes away but the Roon Appliance and RoonServer processes stay around.

Here’s where we are after a restart.

Hey @David_Moor,

Apologies for any confusion!

You’ll want to reboot your Roon Server twice. You can typically stop/quit Roon Server from running via the taskbar on your Mac. Here’s a screenshot:

Screenshot 2024-08-02 at 13.00.05

Benjamin -

I don’t have any Roon icon in my taskbar.

There is another issue which may or not be related to the memory leak. Roon keeps losing its connection to the server. When prompted to connect to a different server I chose the same one and it reconnects. Sometimes it will just reconnect without my doing anything.

Uploaded log files.

Hi @David_Moor,

My apologies here, but which device are you currently running as your Roon Server? The same device you’ve shared a screenshot of in your response above, correct?

How do you typically start and stop Roon Server running on your Mac? Or, are you running Roon Server on a different machine? That would explain why you’re not seeing Roon Server via your mac task bar.

Either way, reboot your Roon Server twice and let me know when you’re back up and running, our team will pull a fresh diagnostic report for an additional review. :+1:

Benjamin -

Running on the same device, my Mac Studio.

Rebooted 2x. Do these reboots have to occur consecutively or can they be spaced out over time?

After some additional reboots unable to use Roon at all. My SoundID and Mac audio zones have completely disappeared. They do work in Qobuz.

Logs uploaded.

Uninstalled and reinstalled Roon hoping to get the local devices on my Mac to show. No luck. Only an airplay option to my Mac and 6 HDA Intel devices. No System default, Studio Display speakers, Oppo HA-1, Mac Studio Speakers, or SoundID Reference targets.

All 5 devices show in Tidal. Qobuz has 4 - doesn’t have system default.

Hi @David_Moor,

Thanks for the clarification. A normal uninstall / reinstall won’t do much, lets see if refreshing your database helps in the meantime. Please make a fresh back up of your current database for safe keeping.

Then, follow the below directions:

  • Make a Backup of your current RoonServer Database
  • Exit out of RoonServer
  • Navigate to your RoonServer’s Database Location
  • Find the folder that says “RoonServer” and “Roon”
  • Rename the “RoonServer” folder to “RoonServer_old” and to “Roon_old”
  • Reinstall the RoonServer App from our Downloads Page to generate a new RoonServer folder
  • On the Roon Remotes, press “Use another Roon Server” and connect to the new database

See if you’re able to gain access to your audio devices before restoring from a backup. I’d double-check your mac firewall settings as well to ensure Roon, Roon Server and RAATServer is listed as proper exceptions. :+1:

Hi @David_Moor,

Update here to keep you posted - the team’s investigation is ongoing but we’re continuing to make progress with developers. Thanks for your patience.

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

Hi @David_Moor,

The team has shipped a potential fix for an underlying mechanism here. Are you still experiencing the same symptoms on the most recent release?

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