A hotfix is available that resolves some memory leak issues for WPF in the .NET Framework 3.0 SP2
Note The .NET Framework 3.0 SP2 is contained in the Microsoft .NET Framework 3.5 Service Pack 1 (SP1).
Issue 1You run a WPF application that contains styles or templates that refer to application resources by using the StaticResource markup extension or the DynamicResource markup extension. Many controls that use these styles or templates are created. However, these controls do not use the referred resources. In this situation, the memory of some DeferredAppResourceReference objects is leaked after garbage collections free the controls.
Issue 2You run a WPF application that contains controls whose properties are data-bound to DependencyObject objects. The lifetime of the objects is longer than the lifetime of the controls. When many controls are created, the memory of some WeakReference objects and of holding array spaces is leaked after garbage collections free the controls.
Issue 3You run a WPF application that uses TreeView controls or controls that are derived from the Selector class. The controls register an internal notification to control keyboard focus in the KeyboardNavigation class. The application creates many of these controls. For example, you add and then delete these controls. In this example, the memory of some WeakReference objects and of holding array spaces is leaked after garbage collections free the controls.
2667241 An update rollup is available for Windows Presentation Foundation (WPF) for Microsoft .NET Framework 3.5
Article ID: 981107 - Last Review: 04/10/2012 05:57:00 - Revision: 2.0
- kbexpertiseadvanced kbsurveynew kbqfe kbHotfixServer KB981107