RoonServer OOM-Kills on 32-Core Machine with Ubuntu 24.04 LTS (ref#BC92TE)

Thanks for sending those over!

Unfortunately, no. If you could please upload the full Varlog for our development team, it would be more helpful to learn whats occurring around the entire picture versus the selected snippets shared so far.

A few follow-up questions in the meantime:

  1. If you disable analysis in Roon Settings>Library and disable both analysis options, do you still run into the same OOM error?
  2. If you only import Tidal/streaming service content alone, OR, only local content (Not simultaneously) does the same error occur?

Thanks for your cooperation! :+1:

If you disable analysis in Roon Settings>Library and disable both analysis options, do you still run into the same OOM error?

This support process is incredibly frustrating because you seem to just be guessing at things. It’s even more frustrating when they’re guesses we’ve already been through. Both analysis options have been disabled for 20 days now, since the first time I was asked to disable them.

If you only import Tidal/streaming service content alone, OR, only local content (Not simultaneously) does the same error occur?

I started with only Tidal. Roon was able to play music from Tidal for about sixty seconds before stopping entirely and reporting “Tidal media is loading slowly…” for every track. The Tidal client is fine streaming on the same machine. I’m not sure what adding another, new problem does to help us in troubleshooting.

Disabling Tidal and using only local files results in the previously observed symptoms – memory consumption climbs steadily while it imports local files very, very slowly.

Any updates?

Hey @Neil_Carpenter,

I’m sorry to hear you’re feeling this way. Unfortunately, in this case, it’s a minor effect caused by the length of the thread. Due to the time and complexity involved, it was important to ensure the variables were in the same condition throughout.

Were you able to send the full varlog file over? Our team isn’t seeing anything on our end.

Since the issue seems to be tied to this specific machine, have you tested running Roon Server on a different device yet? I see you may have a Mac available that may be worth testing out in the meantime.

Thank you!