Roon Nucleus One freezes during music import due to high memory usage (ref#NXGET2)

Support Nucleus Support
1

Select your Nucleus model from the list below

· Nucleus One

I'm having trouble with my Nucleus hardware

· Other

Select the option that fits best

· The Nucleus boots up and I can connect to it in the Roon app without issue, but I have a question about configuration/storage/attached devices

Describe the issue

I have a Roon Nucleus One with a 4TB internal SSD. The Nucleus and Roon Server initially work normally, but when I add/import new music tracks to the internal storage, Roon becomes extremely slow/freezes and the Roon app loses connection to the Server. The problem happens again even when I add only a few tracks.

The Nucleus web administration page still shows the Operating System, Roon Server Software, Database and Internal Music Storage as OK. The server can restart, but the problem returns when music is imported.

I checked the RoonServer logs around the time of the problem. They show very high memory/GC activity (Managed-live around 92–97% of committed memory), long GC pauses, and repeated audio extraction/import activity. I have created a Logs.zip file and can provide it to support.

My internal storage previously contained approximately 35,817 imported tracks. I disabled the watched storage temporarily while troubleshooting. I would like help determining whether this is a Roon Server/database/import issue or a problem triggered by particular music files. Please advise how I can safely restore my library without the server repeatedly freezing/disconnecting.

2

Hi @simon_shoshan,

Thank you for your report. We’ve escalated this report to engineering along with logs.

If you’re able to provide a copy of your Roon database folder, it will greatly expedite our investigation. At your convenience, please use these instructions to locate the Roon Server folder hosting the DB, copy it, compress (zip) the copy, and upload that to our secure servers using this link.

We’ll follow up as soon as we have additional information from development. The team has a fleet of memory and performance improvements that we’re preparing for release over the next few updates.

5

Hello @simon_shoshan ,

It looks like the thread auto-closed before we had a chance to follow up, so I’ve reopened it and have extended the auto-close period. I noticed you also sent the database over, thank you for that. The case is still pending review by the team and we will follow up once we have next steps, thank you.