Memory Leaks and WPF

- tagged

I think that there is an assumption by many .NET developers that, with the CLR's garbage collector, they are immune from memory leaks.  This is hardly the case.  When writing WPF applications, there are a number of gotchas in this department.  Hat's off to Jossef Goldberg, who has a fantastic post on some of the more pernicious WPF memory leaks: how to avoid them and, if that fails, how to find them.  

posted on Feb 7th, 2008 | Permalink | Comments (2)

2 Comments »

  1. Reading Jossef's article only makes me paranoid about my use of WPF, and makes me think that there are many undiscovered issues which could affect performance. Since you work at Microsoft, is there anything that you can say to help me feel more content about my use of XAML and WPF?

    Comment by Deavon Barlow - February 19, 2008 @ 1:13 PM

  2. I'd say this: all platforms have their gotchas. WPF has its set of them. The good news is that we are starting to understand what those gotchas are.

    For the record, I've never ended up writing WPF code that had a memory leak. I think these are edge cases to a certain extent, but when your app is leaking, posts like this are great at helping track them down...

    Comment by Karsten Januszewski - February 21, 2008 @ 5:32 PM

Leave a comment