Eliminating WPF Memory Leaks: Weak Events, Binding Pitfalls & Memory Profiling

When a short-lived view or user control subscribes directly to a long-lived service event (such as ITelemetryService.DataReceived += OnDataReceived;), the publisher holds a strong reference to the subscriber via the delegate's target pointer. Even if the window is closed and detached from the visual tree, the GC cannot collect it because it remains rooted by the singleton service.

When binding to a property of an object that does not implement INotifyPropertyChanged, the WPF binding engine subscribes to TypeDescriptor.GetProperties() to listen for property changes. This causes global static tables inside the runtime to retain references to your ViewModel and attached UI controls for the entire process lifetime.

Static code analysis cannot catch dynamic closure leaks. In production diagnostics, capture a memory snapshot before and after invoking a high-churn workflow (e.g. Opening and closing a secondary monitoring dashboard 20 times). Group surviving objects by retention path to identify the exact rooted reference path.