Roon search and edit performance issues with frequent crashes on Nucleus (ref#RI1PNJ) [Ticket In]

@benjamin mentioned in an earlier post that the team is working on memory optimizations. These are now being tested by community members in Early Access

It’s an ongoing effort.

EarlyAccess: Roon 2.65 Build 1648 and ARC 1.77 Build 401 are Live! - Early Access / Software Release Notes - Roon Labs Community

Hey, @Michael_Putz.

We know this has been a rough stretch, especially with search, edits, and manual backups all becoming unreliable. The memory optimizations we mentioned are still in progress, and they are now being tested by community members in Early Access. Once the next release is pushed live, please circle back with us and let us know how the system is behaving on your end.

Hi @Michael_Putz,

How are things performing for you on the most recent Roon release?

Hi @connor - things are moving faster:

  1. more or less everything regarding search that took the system between 10 and 20 (+) seconds, now shows after 3 to 6 seconds - that is a massive improvement
  2. most editing stuff that took the system between 15 and 30 (+) seconds, now shows after 5 to under 10 seconds - that also is a massive improvement
  3. manual back-up didn’t crash - yeah, finally.

Thanks for this.

As I am approaching the 10.000 albums threshold (will be reached in the next months because I’ve bought a huge record collection that I’ll transfer to roon), I was wondering if the Nucleus Titan would improve the issues even more? If so, how’s the Titan doing speed improvemt exactly?

Thanks and best regards

@alex_h, @vadim , @benjamin , @noris , @connor

I’ve uncuccessfully tried to reach you via direct messages. Now, instead, I try to get feedback by creating a new topic on this. However, this refers to this closed case Roon search and edit performance issues with frequent crashes on Nucleus (ref#RI1PNJ) , which I’d like to to reopen, beacause in the meantime, unfortunately, we are back to square one.

The problems have returned massively—after about two weeks of respite… The only improvement is that there seems to be no full crashes. But painstakingly slow editing and searching is back with unfortunate force.

Editing or searching takes minutes (!) now before being finished. It drives me nuts.

All these problems are worst after weeks of Roon running uninterrupted (the problems do not appear right after having Roon shut down for a day or two - they reappear after days or weeks of uninterrupted use).

All my system details are unchanged.

Some examples of the troubles I’ve had:

May 23rd, 9:51 a.m. CEST local time

Track search on iPad device. The following screenshots show

  • starting a search of a track during playback of a song at 2:31 playback time,

    image

    image2048×1536 203 KB

  • the search doesn’t show results at 0:42 playback time of the next song (with this song’s playback display showing no amplitude)

    image

    image2048×1536 204 KB

  • the search doesn’t show results at 0:51 playback time of the next song (at that point this song’s playback display showing an amplitude for the first time)

    image

    image2048×1536 204 KB

  • the search shows the results finally at 0:59 playback time of the next song (approx. 1.5 minutes after the start of the query)

    image

    image2048×1536 298 KB

May 23rd, 9:56 a.m. CEST local time

Track editing on iPad device. The following screenshots show

Furthermore, I can report (without screenshots) that when I skip to the next song, it plays with a delay of four or five seconds.

Pls help!

Michael

PS: Are there other Roon users with medium-big database (I do have 6,500 albums stored in my local library) and these kind of massive troubles? Also, please reach out… Thnx.

@Michael_Putz - I’ve merged your post into your existing support thread and re-opened it. The tech support team will pick it up and respond here to you.

PS - you mention that you have 6,500 albums stored locally - do you also have albums from a streaming service added to your library? The size of a Roon library is determined by the sum of local and streaming content that has been added to it.

Hi @Michael_Putz,

Thank you for the report and our apologies for the delay. We’ll respond shortly with more conclusive comments after running this by engineering. We still have a copy of the database you provided earlier, so we shouldn’t need anything additional to investigate this latest symptom.

6,500 [albums] stored locally - currently just a few from TIDAL (less than 10). Thnx

Hey @Michael_Putz,

If you could, please perform a fresh reboot of your Roon Server, and then grab a fresh date/time the next time you experience sluggishness.

We’re hoping some additional logging will aid in further analysis. We’ll be monitoring for your reply. Thank you!

@benjamin I’ve rebooted just now & feedback on issues later this week. Stay tuned.

Michael

@benjamin @connor it just took a couple of hours after the reboot, and the first issues occured.

June 16, 15:55 local time: Results of a track search took more than 20 seconds to display.

June 17, 9:55 local time: It took more than 1.5 minutes to open a selected album.

June 17, 13:19 local time: track editor change - saving time took circa 40 seconds to finish up.

It’ll getting worse from day to day (as long as there’s no fresh reboot).

Thanks - M

PS:

Even more annoying is, that it takes more than 15 seconds to skip to the next track!

Example:

(local time: Monday, June 22nd, 10:32 am)

Hey @Michael_Putz.

Thanks for those details, we’ve added this to the development ticket. If more info is needed, we’ll be sure to reach out, thanks!

Thanks for your ongoing patience. We wanted to provide an update after the weekend.

At this time, this ticket remains in the pipeline, but we’ll share more information as it becomes available from development.

There are memory and performance improvements undergoing testing in Early Access that might also help relieve these symptoms for you, although those changes do not reflect the specific ticket tracked by this thread.

Thanks @connor , I’m looking forward to this update. Hope it’ll help.

Two things I’d like to follow up on to:

  1. everytime I do reboot the system (or shut it down and restart a while later) all issues disappear for a day or at least a few hours; however, as roon recommends to keep the system running I am wondering if the quite frequent reboots/on-and-offs are an issue for hard-/sofware?
  2. secondly I’d like to ask my question again that I’ve asked a few months ago but somehow got lost: I was wondering if the Nucleus Titan would improve the issues even more? If so, how’s the Titan doing speed improvemt exactly?

Thanks - Michael

Hey @Michael_Putz,

No, occasional reboots or power cycles won’t damage your Nucleus One’s hardware or corrupt the Roon Server software. SSDs and the rest of the internals are designed to handle many power cycles without wear concerns, that’s not a meaningful risk factor here. The “keep it running” recommendation exists mainly because Roon Server does background work (library scanning, audio analysis, indexing) that’s most efficient when the system stays up, not because power-cycling itself is harmful.

That said, a caveat worth noting from your case specifically:

  • A clean shutdown through the Roon app/web interface is always preferable to unplugging or cutting power abruptly. Your support thread actually flagged dirty/unclean unmounts on two attached USB backup drives (possible filesystem corruption on one), which is the kind of thing abrupt power loss, not a proper reboot, can cause. Rebooting properly via Settings is safe.

Short answer: likely yes for headroom, but it’s not guaranteed to fix the specific bug your experiencing.

What the Titan brings over the Nucleus One:

  • ~36% higher CPU performance
  • ~80% increase in RAM speed/memory bandwidth
  • Officially supports libraries beyond 100,000 tracks, versus the Nucleus One's rated ceiling of up to 10,000 albums / 100,000 tracks
  • More robust simultaneous multi-zone playback and DSP handling
Given you're about to cross the 10,000-album mark with your new record collection, you're heading right toward the edge of what the Nucleus One is officially rated for, so the Titan's extra headroom (CPU, RAM, and library capacity) would likely reduce strain as your library grows, and could make general browsing/search snappier at scale.

However, it’s worth being direct about this: the specific slowdown pattern in your thread, performance that’s fine right after a reboot but degrades over hours/days, looks like a software-side memory or resource leak, which the team is still actively working on (the Early Access memory/performance fixes referenced in your last few posts).

More powerful hardware can raise the ceiling before that leak becomes noticeable, but if the underlying leak isn’t fixed, a Titan could still degrade the same way, just take longer to get there. So a Titan upgrade is reasonable for library-growth headroom, but I wouldn’t count on it as a guaranteed fix for the specific bug this ticket is tracking.