Roon Remote hangs on "Initializing" with Core connection and GC pauses (ref#G6GXXS)

Support
1

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· App interface looks or behaves oddly

Tell us what's going on

· Roon Remote hangs on “Initializing” despite immediate Core connection — RoonServer shows 8–14 sec GC pauses

Tell us about your home network

· Nucleus IP: 10.0.0.24, Ethernet-connected to an Orbi satellite
NETGEAR Orbi RBR750P / AX5200 mesh

2

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· App interface looks or behaves oddly

Tell us what's going on

· Roon Remote hangs on “Initializing” despite immediate Core connection — RoonServer shows 8–14 sec GC pauses

Tell us about your home network

· Nucleus IP: 10.0.0.24, Ethernet-connected to an Orbi satellite
NETGEAR Orbi RBR750P / AX5200 mesh

Are GC pauses of 8–14 seconds, including periods where RoonServer spends 90%+ of a 15-second interval in garbage collection, expected under any normal circumstances? Could this be causing the Remote to remain at “Initializing” even though the Remote/Core TCP connection and initial handshake have already succeeded?

If not, what would you recommend investigating next — database/search-index behavior, a database issue, RoonServer/runtime behavior in build 1683, storage performance, or something else?

I can provide additional logs or reproduce the issue with specific diagnostics if helpful.

3

Hi @Bob_Gluck,

Thank you for the detailed report and for digging into the logs!

To answer your question directly: GC (Garbage Collection) pauses of 8–14 seconds are unusually long. While memory management is a standard part of Roon’s background operations, spending 90% of a 15-second interval in GC indicates severe memory pressure.

However, we typically have not seen GC pauses cause the Remote to hang indefinitely on the “Initializing” screen once the initial TCP handshake has already succeeded.

If this behavior is strictly tied to memory pressure and those long GC pauses, a simple reboot of the Nucleus should clear the accumulated state and allow the Remote to connect normally, at least for a period of time.

Could you let us know if a reboot temporarily resolves the issue, or if this “Initializing” hang is a constant, permanent state every time you open the app?

To investigate exactly what is happening with the runtime and database, please note the exact date and time (including your local time zone) the next time the Remote hangs on this screen. Once you provide that timestamp, we will pull diagnostics from your Nucleus to see exactly what is tying up the Core during that specific window.