Comments on: Silverlight’s ProgressBar And Possible Memory Leaks http://davybrion.com/blog/2009/02/silverlights-progressbar-and-possible-memory-leaks/ Trying to walk that thin line between intelligence and ignorance Thu, 29 Jul 2010 20:29:49 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Davy Brion http://davybrion.com/blog/2009/02/silverlights-progressbar-and-possible-memory-leaks/comment-page-1/#comment-9290 Davy Brion Mon, 02 Mar 2009 18:11:13 +0000 http://davybrion.com/blog/?p=1012#comment-9290 @Rob i didn't even know you could load sos in the immediate window :) @Rob

i didn’t even know you could load sos in the immediate window :)

]]> By: Rob http://davybrion.com/blog/2009/02/silverlights-progressbar-and-possible-memory-leaks/comment-page-1/#comment-9289 Rob Mon, 02 Mar 2009 18:10:14 +0000 http://davybrion.com/blog/?p=1012#comment-9289 By the way, cool thing finding the bug. By the way, cool thing finding the bug.

]]> By: Rob http://davybrion.com/blog/2009/02/silverlights-progressbar-and-possible-memory-leaks/comment-page-1/#comment-9288 Rob Mon, 02 Mar 2009 18:09:35 +0000 http://davybrion.com/blog/?p=1012#comment-9288 Why would you use windbg (beside it's coolness factor)? You can just as well load Sos in your immediate window in VS (.load sos) Why would you use windbg (beside it’s coolness factor)? You can just as well load Sos in your immediate window in VS (.load sos)

]]> By: Samuel Jack http://davybrion.com/blog/2009/02/silverlights-progressbar-and-possible-memory-leaks/comment-page-1/#comment-9210 Samuel Jack Fri, 27 Feb 2009 09:23:35 +0000 http://davybrion.com/blog/?p=1012#comment-9210 I had a a similar bug with the WPF progress control when it was in indeterminate mode. It was a bit weirder though, because this bug would cause memory allocations of about 4k/sec starting from a few seconds after you closed the form containing the progress bar! It wasn't as simple as it holding onto the parent object though: IIRC the allocations were all happening inside one of the unmanaged parts of WPF. I could never get a reliable reproduction of it though, so I haven't been able to submit a bug to MSFT yet. In the end, I went with making a text based control of my own, shunning WPF animation in this scenario. I had a a similar bug with the WPF progress control when it was in indeterminate mode. It was a bit weirder though, because this bug would cause memory allocations of about 4k/sec starting from a few seconds after you closed the form containing the progress bar! It wasn’t as simple as it holding onto the parent object though: IIRC the allocations were all happening inside one of the unmanaged parts of WPF.

I could never get a reliable reproduction of it though, so I haven’t been able to submit a bug to MSFT yet.

In the end, I went with making a text based control of my own, shunning WPF animation in this scenario.

]]> By: Justin-Josef Angel http://davybrion.com/blog/2009/02/silverlights-progressbar-and-possible-memory-leaks/comment-page-1/#comment-9185 Justin-Josef Angel Thu, 26 Feb 2009 18:34:17 +0000 http://davybrion.com/blog/?p=1012#comment-9185 Hi Davy, Thanks, we've got an internal bug open on that and we're trying to get this fixed for vNext. Thanks for blogging about this. It's important for the community to generate this kind of knowledge. Sincerely, -- Justin Angel Microsoft Silverlight Toolkit program manager Hi Davy,

Thanks, we’ve got an internal bug open on that and we’re trying to get this fixed for vNext.

Thanks for blogging about this. It’s important for the community to generate this kind of knowledge.

Sincerely,
– Justin Angel
Microsoft Silverlight Toolkit program manager

]]>