Select the product you need help with
A hotfix is available that resolves some memory leak issues for WPF in the .NET Framework 4Article ID: 2297328 - View products that this article applies to. On This PageSYMPTOMSA hotfix is available that resolves the following memory leak issues for Windows Presentation Foundation (WPF) in the Microsoft .NET Framework 4. 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 WeakReference objects and of the holding array space 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.RESOLUTIONA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website: http://support.microsoft.com/contactus/?ws=support Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
(http://support.microsoft.com/contactus/?ws=support)
Note You can download this hotfix rollup from the following Microsoft Connect Web site: http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=31847
(http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=31847)
PrerequisitesThe following list contains prerequisites for this hotfix package:
Restart requirementYou do not have to restart the computer after you apply this hotfix if affected files are not being used.Hotfix replacement informationThis hotfix package does not replace a previously released hotfix package.File InformationThe English (United States) version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.For x86 versions of Windows XP, of Windows Server 2003, of Windows Vista, of Windows Server 2008, of Windows 7, and of Windows Server 2008 R2: Collapse this table
Collapse this table
MORE INFORMATIONFor information about similar issues with the .NET Framework 3.5 Service Pack 1 (SP1), click the following article number to view the article in the Microsoft Knowledge Base: 981107
(http://support.microsoft.com/kb/981107/
)
A hotfix is available that resolves some memory leak issues for WPF in the .NET Framework 3.0 SP2STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. PropertiesArticle ID: 2297328 - Last Review: October 29, 2010 - Revision: 2.0
| Article Translations |
Back to the top
