|
|
|
Use this tool to learn about websites, specifically the one you just entered. If you find some aspect of it inappropriate it is not our fault. If you are the owner of this website: yes we are a real search engine, we do have a real web crawler called FyberSpider and you can block it if you feel the urge.
We are in the process of updating this tool. Until we are done just use our search results to check the inclusion status of your site.
Arno's Software Development Weblog
This is just a sample of the content found on this website. Please visit the website to read the entire page. "Arno's Software Development Weblog http://arnosoftwaredev.blogspot.com/ en noreply@blogger.com (Arno) Fri, 26 Jun 2009 14:30:47 PDT Blogger http://www.blogger.com 316 1 25 This is an XML content feed. It is intended to be viewed in a newsreader or syndicated to another site. Composite WPF ("Prism") DelegateCommand.CanExecuteChanged Memory Leak http://feedproxy.google.com/~r/ArnosSoftwareDevelopmentWeblog/~3/GKfM3TPlVNY/composite-wpf-prism-delegatecommandcane.html noreply@blogger.com (Arno) Wed, 24 Jun 2009 09:28:41 PDT tag:blogger.com,1999:blog-8490763.post-4686662270263598186 I was happy to hear that the <a href="http://msdn.microsoft.com/en-us/practices/default.aspx">Microsoft Patterns and Practices Team has picked up <a href="http://compositewpf.codeplex.com/WorkItem/View.aspx?WorkItemId=4065">this Composite WPF ("Prism") bug report that I submitted several weeks ago. From the issue description:<br /><br />When profiling my application I noticed that plenty of EventHandlers had never been deregistered from DelegateCommand's CanExecuteChanged-Event. So those EventHandlers were never been garbage-collected, which caused a severe memory leak.<br /><br />As registering CanExecuteChanged-EventHandles is done outside application code scope I had expected them to be deregistered automatically as well. At this point I thought this might as well be a ThirdParty WPF control issue, but digging further I read a blog post stating that "WPF expects the ICommand.CanExecuteChanged-Event to apply WeakReferences for EventHandlers". I had a look into RoutedCommand, and noticed it uses WeakReferences as well.<br /><br />Now this is no showstopper for us as we are very early in the development cycle, and we simply patched <a href="http://msdn.microsoft.com/en-us/library/cc707894.aspx">DelegateCommand in the meantime by using <a href="http://msdn.microsoft.com/en-us/library/system.weakreference.aspx">WeakReferences for its &l" .... read entire page
|
|
|