Confusing WPF results. Any ideas?

• 
  We do only show the shortest paths in the object reference graph at the moment: we're planning to look at new ways of exploring the graph in future versions. However, the roots that we do show are only the strong roots for an object: weak roots (and hence weak references) are deliberately excluded from the graph, as there are usually too many of these in WinForms or WPF applications for the graph to make any sense.
  
  You can use the class reference graph to explore the full relationships between objects, and switch to the object list or graph when you find something interesting there. The filters can be useful for narrowing down cases where there are a lot of similar objects. For a UI library like WPF you typically find that everything eventually references everything else in some way - it's for this reason that we prefer to use the shortest path, as when there's a loop of references, the objects nearer to a root are typically nearer to the 'start' of the loop as seen from the point of view of the program.
  
  The object graph highlights any objects that make a loop in a blue box - any objects so highlighted have a path linking them in both directions - typically through parent/child fields but sometimes via more complicated paths.

  Andrew H June 16, 2009 06:23

  - 0 +
• 
  Thanks for the info.
  
  I've now discovered the cause of my confusing results, in case it helps anyone.
  
  Localization._attributesOnObjects is the storage used when the Localization.Attributes attached property is set on an object that isn't a DependencyObject. In our case we were setting it on some DataTemplates and HeirarchicalDataTemplates to stop our L18n tool's automatic simulated translation messing them up. That turns out to have been a bad idea.
  
  System.ComponentModel.ReflectPropertyDescriptor turned out to be a signpost to a genuine WPF memory leak, as described here: http://support.microsoft.com/kb/938416
  
  In our case we're doing View-PresentationModel (similar/same as MVVM) and some of our PMs weren't implementing INotifyPropertyChanged. As the View & the PM reference each other, that was triggering the leak. Implementing INotifyPropertyChanged or setting the Mode of the view's bindings to the PM to OneTime fixes the leak.
  
  Many, many thanks again for v5. I can't imagine how I would have tracked all this down without it.
  
  Is there any way of extending the trial of the RC? Mine's about to run out, but we've got 10 full ANTS ".Net Bundle" licences (with 1 year's worth of free upgrades) that we bought in Dec/Jan.

  swythan June 17, 2009 10:22

  - 0 +
• 
  Hi James,
  
  Very glad that you found the cause of the problem and that the new version has proved such a success for you.
  
  The final V5.0 release is due out tomorrow so you will be able to download and use it from then on as the activation/licensing will work with your key etc...
  
  Regards,
  
  Stephen

  StephenC June 17, 2009 10:41

  - 0 +
• 
  Brilliant! I swear you guys are reading my mind!

  swythan June 17, 2009 11:52

  - 0 +

Add comment

Please sign in to leave a comment.