Roon Is Incredibly Slow and Close to Unusable over last days please help with dropouts when it does work and with other devices looking for Roon core for very long periods

Steven_Wechsler · November 11, 2022, 9:00pm

Roon Core Machine

Roon Core is running on iMac Big Sur 117 with 32 GB memory 3.7 GHz i5

Networking Gear & Setup Details

My router is Verizon Quantum Gateway
Model is Fios-G1100
Also use Linksys Mesh WiFi network WHW03 (Base unit plus 4 additional)
No VPN, proxy servers, etc.

Connected Audio Devices

Roon Core iMac is connected by ethernet to Linksys mesh network, then out to PS Audio Directstream (with network ethernet bridge card installed) through netgear network switch.

Roon non-Core is installed on Mac laptop and another iMac as well as Roon Remote on my iPhone 11
for use through wifi network

Number of Tracks in Library

55,000 tracks

Description of Issue

For the last week or so, Roon has been incredibly slow, buggy and prevalent with dropouts, stutters, etc.
Happen on Roon core machine as well as all others. Sometimes it takes forever to find a track. Doesn’t matter if track is streamed via Tidal or Qobuz or accessed via Roon core internal hard drive or external hard drive. All the same. Streaming Tibal or Qobuz through their own independent apps works just fine. Sometimes it says Qobuz or Tidal doesn’t have track (when it does). Sometimes it says on other machines “waiting for your Roon Core”. Listening right now from Roon Core one song stops and starts multiple times. Sometimes it skips half the song and goes to another song. Totally unreliable. No idea what has happened. Network in home works fine for all else, including 4k streaming, etc.

Andrew_Munro · November 11, 2022, 11:06pm

I had similar issues to what you are describing but with a very different set up. Had to completely factory reset my NAS and reinstall everything to get it working again. Have you tried switching your roon core location (I switched it to my laptop)? Would not be a solution but may help you narrow down where the issue is.

Robert_F · November 12, 2022, 2:48am

@Steven_Wechsler, what you are experiencing may be symptomatic of issues in your home network. Are any of your Linksys mesh devices connected by Ethernet cables to your main Linksys router, or are they all connected via WiFi to each other (with the base Linksys unit connected by Ethernet cable to the Verizon router?)?

Relative to your Linksys mesh units, are all of your mesh units connected directly to the main Linksys router, or do you have mesh units connected to other mesh units? The Linksys Velop system you have is pretty, but how it is deployed around your home may have some limits to the capacity of each connection, and therefore may result in issues in seeing Roon’s core consistently.

Diederik_Cabri · November 12, 2022, 12:32pm

This started for me after the upgrade to 2.0.3 on macOS 12.6.1 (21G217) on MacPro6,1 6-Core Intel Xeon E5 3,5 GHz 6 Cores with Memory: 32 GB dedicated to RoonServer computer.

Very unstable version, seems like a rush job. Totally filled with newly added bugs over 2.0.2.
Most significant is raat daemon that crashes, then RoonServer tries endless loop to reconnect to it on 127.0.0.1:someport, and the routing is endlessly calling itself. Finally, after enough calls to itself, it blows out of memory and crash dumps.

Stack overflow.
at System.Text.StringBuilder.ExpandByABlock(Int32)
at System.Text.StringBuilder.Append(Char*, Int32)
at System.Text.StringBuilder.Append(Char[], Int32, Int32)
at System.IO.StreamReader.ReadToEnd()
at System.IO.File.InternalReadAllText(System.String, System.Text.Encoding)
at System.Net.NetworkInformation.UnixIPInterfaceProperties.GetDnsAddresses()
at System.Net.NetworkInformation.BsdIpInterfaceProperties…ctor(System.Net.NetworkInformation.BsdNetworkInterface, Int32)
at System.Net.NetworkInformation.BsdNetworkInterface…ctor(System.String, Int32)
at System.Net.NetworkInformation.BsdNetworkInterface+Context.GetOrCreate(Byte*, Int32)
at System.Net.NetworkInformation.BsdNetworkInterface.ProcessLinkLayerAddress(Void*, Byte*, LinkLayerAddressInfo*)
at Interop+Sys.EnumerateInterfaceAddresses(Void*, Void (Void*, Byte*, IpAddressInfo*), Void (Void*, Byte*, IpAddressInfo*, UInt32*), Void (Void*, Byte*, LinkLayerAddressInfo*))
at Interop+Sys.EnumerateInterfaceAddresses(Void*, Void (Void*, Byte*, IpAddressInfo*), Void (Void*, Byte*, IpAddressInfo*, UInt32*), Void (Void*, Byte*, LinkLayerAddressInfo*))
at System.Net.NetworkInformation.BsdNetworkInterface.GetBsdNetworkInterfaces()
at Sooloos.IPAddresses.GetSubNets()
at Sooloos.IPAddresses.TryGetLocalInterfaceAddress(System.Net.IPAddress, System.Net.IPAddress ByRef)
at Sooloos.Audio.Mdns.MdnsDiscovery._CacheHostname(System.String, System.Net.IPAddress, System.Net.IPAddress, System.Collections.Generic.HashSet`1<Sooloos.Audio.Mdns.MdnsDiscoveryData>)

Another issue is new dropouts. This is from a fully 1Gbps wired connection between Roon server and CXNv2 dedicated Roon player:

11/12 11:07:29 Trace: [Cambridge Audio CXNv2 @ 172.16.1.109:45167] [raatclient] GOT [709] {“status”:“Dropout”,“samples”:26880}
11/12 11:07:29 Trace: [CXN] [zoneplayer/raat] too many dropouts. stopping stream
11/12 11:07:29 Warn: [CXN] [zoneplayer/raat] Too many dropouts (>3s dropped out in the last 30s). Killing stream
11/12 11:07:29 Info: [audio/env] [zoneplayer → stream] All streams were disposed
11/12 11:07:29 Trace: [CXN] [zoneplayer/raat] Endpoint Cambridge Audio CXNv2 State Changed: Playing => Prepared

And in the txt file:
1/12 13:15:57 Debug: [raat/tcpaudiosource] connecting to 172.16.1.109:34104
11/12 13:15:57 Debug: [raat/tcpaudiosource] connected
11/12 13:44:28 Debug: [raat/tcpaudiosource] disconnecting
11/12 13:44:28 Warn: [raat/tcpaudiosource] send failed: Arg_NullReferenceException
11/12 13:44:28 Warn: [raat/tcpaudiosource] disconnecting + retrying
11/12 13:44:29 Debug: [raat/tcpaudiosource] connecting to 172.16.1.109:34104
11/12 13:44:29 Debug: [raat/tcpaudiosource] connected
11/12 13:51:59 Debug: [raat/tcpaudiosource] disconnecting
11/12 13:51:59 Warn: [raat/tcpaudiosource] send failed: Arg_NullReferenceException
11/12 13:51:59 Warn: [raat/tcpaudiosource] disconnecting + retrying
11/12 13:52:04 Debug: [raat/tcpaudiosource] connecting to 172.16.1.109:34104
11/12 13:52:04 Debug: [raat/tcpaudiosource] connected
11/12 13:58:12 Warn: [raat/tcpaudiosource] send failed: Broken pipe
11/12 13:58:12 Warn: [raat/tcpaudiosource] disconnecting + retrying
11/12 13:58:12 Debug: [raat/tcpaudiosource] disconnecting

followed by 50 or more times:
11/12 13:58:12 Debug: [raat/tcpaudiosource] connecting to 127.0.0.1:49275
11/12 13:58:12 Error: [raat/tcpaudiosource] connect failed: Connection refused
11/12 13:58:12 Warn: [raat/tcpaudiosource] disconnecting + retrying
11/12 13:58:12 Debug: [raat/tcpaudiosource] disconnecting
11/12 13:58:12 Debug: [raat/tcpaudiosource] connecting to 127.0.0.1:49275
11/12 13:58:12 Error: [raat/tcpaudiosource] connect failed: Connection refused
11/12 13:58:12 Warn: [raat/tcpaudiosource] disconnecting + retrying
11/12 13:58:12 Debug: [raat/tcpaudiosource] disconnecting
.
.
.

And finally crash (out of memory?).

Then there is the error with (on an all wired 1Gbs connection) drop outs with my CXNv2 :

11/12 13:08:25 Trace: [Cambridge Audio CXNv2 @ 172.16.1.109:45167] [raatclient] GOT [2988] {"samples":25751,"status":"Dropout"}
11/12 13:08:25 Trace: [Cambridge Audio CXNv2 @ 172.16.1.109:45167] [raatclient] GOT [2988] {"samples":49920,"status":"Dropout"}
11/12 13:08:25 Trace: [Cambridge Audio CXNv2 @ 172.16.1.109:45167] [raatclient] GOT [2988] {"samples":48000,"status":"Dropout"}
11/12 13:08:25 Trace: [CXN] [Enhanced 87,7x, 24/96 FLAC => 32/96] [100% buf] [PLAYING @ 0:25/6:00] Shipyard - Sting / Jimmy Nail / Brian Johnson / Jo Lawry
11/12 13:08:27 Trace: [Cambridge Audio CXNv2 @ 172.16.1.109:45167] [raatclient] GOT [2988] {"samples":48000,"status":"Dropout"}
11/12 13:08:27 Trace: [Cambridge Audio CXNv2 @ 172.16.1.109:45167] [raatclient] GOT [2988] {"samples":48000,"status":"Dropout"}
11/12 13:08:27 Trace: [Cambridge Audio CXNv2 @ 172.16.1.109:45167] [raatclient] GOT [2988] {"samples":48000,"status":"Dropout"}
11/12 13:08:27 Trace: [Pagane] [HighQuality, 16/44 ALAC => 24/44] [100% buf] [PLAYING @ 0:08/3:56] I Write the Songs - Barry Manilow
11/12 13:08:27 Trace: [Cambridge Audio CXNv2 @ 172.16.1.109:45167] [raatclient] GOT [2988] {"samples":48000,"status":"Dropout"}
11/12 13:08:27 Trace: [Cambridge Audio CXNv2 @ 172.16.1.109:45167] [raatclient] GOT [2988] {"samples":48000,"status":"Dropout"}
11/12 13:08:27 Warn: [CXN] [zoneplayer/raat] Too many dropouts (>3s dropped out in the last 30s). Killing stream
11/12 13:08:27 Trace: [CXN] [zoneplayer/raat] too many dropouts. stopping stream
11/12 13:08:27 Warn: [CXN] [zoneplayer/raat] Too many dropouts (>3s dropped out in the last 30s). Killing stream
11/12 13:08:27 Trace: [CXN] [zoneplayer/raat] too many dropouts. stopping stream

...

11/12 13:08:27 Info: [audio/env] [zoneplayer -> stream -> endpoint] All streams were disposed
11/12 13:08:27 Info: [zone CXN] OnPlayFeedback StoppedEndOfMediaUnnatural
11/12 13:08:27 Debug: [zone CXN] _Advance (Track)

But: there is absolutely no difference in ‘slow’ or other media, as they all come from exactly the same NAS. RoonServer never did so many, consistent dropouts before.

I personally think here, the problem is nothing slowness of anything else but the RoonServer doing background work, and this is inhibiting timely network sending of packets, reading media, etc.

Guys, this is just some of the new introduced bugs in 2.0.3. RoonServer now also simply stops playing on corrupt audio files, skips songs in the middle of them playing, and more… And all this, whilst 2.0.2 was doing perfectly…

Please, something is very wrong in 2.0.3, so hoping for a fixed version 2.0.4 soon!

Steven_Wechsler · November 12, 2022, 7:01pm

Well, the problem is remedied and had absolutely nothing to do with internet connectivity or my wifi system, etc.

After looking at various Roon settings, I saw that under the Storage setting Roon core was incessantly looking for “iTunes Libraries (Roon 1.2 and older)”. As soon as I disabled that Storage selection, everything started working normally again.

I think it is worth noting that, although I am not completely certain, I believe this problem only began to appear with Roon 2.03.

Don’t know if this is relevant to other issues out there along similar lines.

Elling_Jacobsen · November 12, 2022, 8:21pm

Same issue here. Updated to the newest roonOS build 254 3 days ago on my NUC 8I7BEH2 i7 with 8GB of memory, approx 200.000 tracks. Since then everything is unbearably slow. Must be related to the update since everything else is unchanged and it worked flawlessly before. There is no demanding process running on the NUC as far as I can see, e.g., audio analysis is turned off.

Diederik_Cabri · November 13, 2022, 11:10am

Hello RoonLabs,

I noticed dropouts occur frequently after “Refreshing device list”.
It is indeed very consistent this line appears above every dropout:

11/13 13:07:29 Trace: [raat] [sood] Refreshing device list
11/13 13:07:29 Trace: [raatserver] [sood] Refreshing device list
11/13 13:07:30 Trace: [Cambridge Audio CXNv2 @ 172.16.1.109:38027] [raatclient] GOT [600] {"status":"Dropout","samples":72099}
11/13 13:07:30 Trace: [Cambridge Audio CXNv2 @ 172.16.1.109:38027] [raatclient] GOT [600] {"status":"Dropout","samples":96000}

Diederik_Cabri · November 13, 2022, 11:15am

I see this also now. Who set this to ‘on’ LoL - I set them all to off now too.

RoonServer_log.01.txt:11/13 10:54:41 Trace: [storage] [directory] Begin queuing fs events, ignoreitunes: False, ignoreplaylists: False
RoonServer_log.01.txt:11/13 10:54:41 Trace: [storage] [directory] Begin queuing fs events, ignoreitunes: False, ignoreplaylists: False
RoonServer_log.01.txt:11/13 10:54:42 Trace: [storage] [directory] Begin queuing fs events, ignoreitunes: False, ignoreplaylists: False
RoonServer_log.01.txt:11/13 10:54:42 Trace: [storage] [directory] Begin queuing fs events, ignoreitunes: True, ignoreplaylists: True
RoonServer_log.01.txt:11/13 10:54:42 Trace: [storage] [directory] Begin queuing fs events, ignoreitunes: True, ignoreplaylists: True

fietser · November 13, 2022, 11:43am

Better start your own support request.

Diederik_Cabri · November 13, 2022, 3:15pm

Settings -> Background Audio Analysis Speed
I also set this to Off.

Seems like Audio Analysis daemon is sometimes failing,
resulting in the whole system waiting and trying to connect to the ‘audio analyser’ (127.0.0.1:xxxx),
and trying and trying, and… crash.

This feature is quite useless IMHO anyway, because I can imagine you can audio analyse a few thousand songs. But when a database reached hundreds of thousands, it will NEVER achieve to analyse all songs.

‘on-the-fly’ analysis does the job just as well.

Anyway: no more crashes, drop-outs, etc. Thank you, Steve, for your research.
Thanks everyone else too. Just too bad we have to disable RoonServer functionality to get a normally working server in 2.0.3 (before Servers worked perfectly).

system · November 15, 2022, 3:16am

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