Hi @Mel_Martin,
Thank you for your patience.
The team has reviewed this case closely to provide a thorough update and some options for moving forward. Here’s where we stand
- Diagnostic logging doesn’t indicate any recent memory spikes or crashes associated with the dropouts you’ve reported here. The dropouts we do see occur when Roon receives a blank port assignment for the TCP connection to networked Zones. A reboot of either Roon or the affected Zone would temporarily resolve the issue by creating a new network discovery process.
This actually matches the disconnection we saw in logs when you reported a similar event back in May of 2021. Do you have the same underlying network as in that report?
- We have seen memory spikes in the past in some of the logs associated with your reports here on Roon Community. These memory events tended to crop up when you played particularly large playlists. We have a constellation of fixes for memory stress that we’ve recently bundled into the latest Early Access release.
We’d like to ask if you want to migrate your Roon Server and Remotes to the Early Access branch to try this new release. It might release some of the symptoms if there is, in fact, memory pressure.
Here are instructions for migrating to Early Access: https://help.roonlabs.com/portal/en/kb/articles/roon-early-access-program
However, we cannot stress enough that certain dropouts visible in logs are the result of unexpected network discovery handling by this network. Something in your network setup is interfering with Roon’s communication with networked Zones. This has likely been happening for years and exacerbating many of the dropout-related issues you’ve had.
We can almost certainly relieve the underlying issue, or at least improve things, if you can share some of the details of your actual network topology and settings. Can you please elaborate on your actual network pathway here?
We’ll watch for your response. Thank you!