2026.3.13 - UI freezes 4-5 s when selecting a large folder (O(n*m) in ExpandConnectionsForCheckoutSelection)
Environment:
RDM 2026.3.13.0 64-bit, .NET 10.0.12, Windows
Data source: Devolutions Server, cache mode File, ~10,100 entries
Folder "DC FASTER" contains ~5,800 entries, several thousand of them are folders (Group)
Problem:
Selecting this folder in the navigation tree freezes the UI thread for 4-5 s (one CPU core at 100 %). Selecting a sibling folder with few subfolders, or the vault root, is instant. Dashboard tab, documentation and folder names have no effect. Disabling "Enable entry states (locked, running, checked out)" does not help.
Profiling (dotnet-trace, UI thread, 2 clicks = 9.4 s):
TreeDataGrid.OnPointerPressed
> FrmMainDocumentManager.LoadConnectionDetailsInControl
> FrmMainDocumentManager.SetControlStates
> ConnectionControlStates..ctor
> BaseConnectionControlStates.SetCheckoutInfo (9.0 s)
> BaseConnectionControlStates.ExpandConnectionsForCheckoutSelection
> <ExpandConnectionsForCheckoutSelection>g__TryAdd|181_0
> InternalConnectionList.FindConnectionsInGroup(string) (9.0 s)
> Enumerable.Where(...).ToArray() (SpanHelpers.SequenceEqual)
FindConnectionsInGroup appears to do a linear scan over all entries for every subfolder in the selection, i.e. O(folders x entries), on the UI thread.
Expected:
Folder selection should not recursively expand the whole subtree for checkout state (or use an indexed lookup / run it off the UI thread).
The trace file (rdm.nettrace, zipped) is attached.
Hello Lukas,
Thank you for the detailed report and the trace.
We analyzed it and confirm your findings: almost all of the freeze is spent in FindConnectionsInGroup, called from ExpandConnectionsForCheckoutSelection on the UI thread. We have escalated it to our QA team, and we will update you once we have a ticket reference or a fix version.
Until then, the only way to reduce the freeze is to have fewer subfolders under a single folder.
Could you also confirm your Devolutions Server version?
Best regards,
Carl Marien
Hello,
This issue will be fixed in version 2026.3.14.0.
Regards
Jonathan Del Signore