Description
Describe the bug
I used Windbg to analyze Dump file. However, due to limited ability, it is impossible to judge where the problem lies.
But I'm not sure if this "FellowOakDicom.Network.DicomServer`1+RunningDicomService" holds a reference.
To Reproduce
I use WorklistSCU call WorklistSCP 5 times, SCP return empty data or mock data, then use dotnet-dump to create dump file, then use Windbg to analyze. Use Windbg commd "!dumpheap -stat", and find "WorklistService" keyword, you can see it have 5 count.
May be this reproduce can't fully reflect the real situation, but it looks like "WorklistService" reference is growing, not release.
Expected behavior
Screenshots or test DICOM files
Environment
Fellow Oak DICOM version: 5.0.3
OS: Windows Server 2016 Datacenter x64
RAM: 32GB
Platform: .NET 6
Please help me, thank you -:), and forgive me for my poor English.