I've a different experience. Bindings are quite leaky and you have to be aware that that when you bind to ObservableCollections (or any collection that implements INotifyCollectionChanged) the bindign will create a strong reference, which will cause memory leaks if your collection has a different life than your UIElement. That's the main cause, but not the only one.
Have a look at this post for more details: http://blogs.msdn.com/delay/archive/2009/03/19/silverlight-charting-is-faster-and-better-than-ever-silverlight-toolkit-march-09-release-now-available.aspx and http://blogs.msdn.com/delay/archive/2009/03/11/where-s-your-leak-at-using-windbg-sos-and-gcroot-to-diagnose-a-net-memory-leak.aspx I recently gave a talk that covers memory leaks in Silverlight. I don't know if they video will be available, but I'll let you know. I just restarted my blog, so I'll post something really soon, including sample code and tips on how to debug it. I haven't seen this covered in many blogs. All of them refer you to WinDbg and SOS (which will become your best friend), but they don't cover real world escenarios. Also check the CLR Profiler, altough I really don't like it, it could help, specially for small apps. -------------------------------------------------------------------------------- Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozsilverlight Other lists you might want to join: http://www.codify.com/lists
