For SciChart WPF, first confirm the leak is real by watching total memory over time, since .NET's garbage collector can make usage look like it is climbing when it is not. Once you are confident there is a genuine leak, use a memory profiler, such as SciTech Memory Profiler, dotMemory, or ANTS, to take a snapshot and trace the shortest path to GC roots. This shows exactly what is holding a reference and preventing collection.
Common culprits of memory leaks include static dictionaries, lists, or variables that are never cleared, and event handler subscriptions that are never unsubscribed. Also check for deadlocked threads or blocked finalizers, and be aware that the x:Name markup extension can sometimes hold an unexpected reference. In most cases, disposing of a SciChartSurface correctly and unsubscribing from events
resolves the memory leak without further intervention, since SciChart is designed to release unmanaged resources automatically once no references remain. Calling .Dispose() explicitly on SciChartSurface can be a good idea, as it immediately releases unmanaged DirectX resources.