Article ID: 967634 - View products that this article applies to.
You may experience one of the following issues when you render graphics by using Windows Presentation Foundation (WPF) in a .NET Framework 3.5 Service Pack 1 (SP1)-based application.
Issue 1When you change the value of the VisualBrush.Visual property in a WPF application, the application crashes.
Issue 2A memory leak occurs in the render thread of a WPF application when you perform one of the following actions:
Issue 3WPF applications that use layered windows crash when you perform one of the following actions:
Cause 1This issue occurs because a generic error is returned from a render thread when the operations in the thread are ordered incorrectly. These operations cause child objects to detach from a null parent object.
For example, a Visual object must be removed from a VisualBrush object before it is detached from the VisualBrush object. However, the operations to remove the Visual object may be ordered incorrectly. Therefore, the Visual object detaches from a null parent object.
Cause 2This issue occurs because of a reference counting error in the render thread.
Cause 3This issue occurs because a Win32 error code is handled incorrectly.
To resolve this issue, apply the hotfix package that is described in the following Microsoft Knowledge Base article:
(http://support.microsoft.com/kb/2667241 / )An update rollup is available for Windows Presentation Foundation (WPF) for Microsoft .NET Framework 3.5
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 967634 - Last Review: April 10, 2012 - Revision: 3.0