WPF RenderTargetBitmap still leaking, and badly!

Welcome, guest Sign in | Your Profile | Help

HOME

YOUR DASHBOARD

CONNECTION DIRECTORY

Visual Studio and .NET Framework - Home Downloads Feedback Surveys

WPF RenderTargetBitmap still leaking, and badly! by Mike Pelton

Closed

as External Help for as External

Type:	Bug
ID:	410590
Opened:	2/3/2009 7:27:27 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

Repeated calls to Render on RenderTargetBitmap eat memory - the GC reports no loss but the working set increases at a rate related to the complexity of the scene - calling Render of a 3D view eats numbers of megabytes per call. RenderTargetBitmap leaks were supposed to be fixed in .NET 3.5 SP1. Very simple code to illustrate is below - watch the memory allocation in Task Manager.

Details (expand)

English

Visual Studio 2008 SP1

Windows Vista

English

Code attached

Loss of hundreds of kilobytes per render call

Loss of no kilobytes per call

N/A

2 attachments

Window1.xaml

Window1.xaml.cs

Posted by Microsoft on 2/3/2009 at 9:04 PM

Thanks for your feedback.

We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you,
Visual Studio Product Team

Posted by Microsoft on 3/13/2009 at 5:26 PM

There are two separate issues causing this problem. There was a bitmap leak in the WPF render thread that was responsible for the large portion of the leak, which has been fixed. The fix will be available in a future release. There also seems to be an issue in the video driver that is still causing a small leak. That issue is currently being investigated.