Posted
on Sep 2, 2010
(permalink)
Using 2010.2.812.1040
Simply placing (and making visible at some point) a RadColorPicker on a page causes the entire visual tree of controls to become pinned in memory. No custom templates, no property settings or event handlers.
From windbg:
DOMAIN(0B745520):HANDLE(Pinned):26512f8:Root: 09f2de80(System.Object[])->
08f8ad84(System.Collections.Generic.Dictionary`2[[System.IntPtr, mscorlib],[System.Object, mscorlib]])->
0ae098a0(System.Collections.Generic.Dictionary`2+Entry[[System.IntPtr, mscorlib],[System.Object, mscorlib]][])->
092292f0(System.Windows.Controls.Grid)->
09229354(System.Collections.Generic.Dictionary`2[[MS.Internal.IManagedPeerBase, System.Windows],[System.Object, mscorlib]])->
092293a0(System.Collections.Generic.Dictionary`2+Entry[[MS.Internal.IManagedPeerBase, System.Windows],[System.Object, mscorlib]][])->
092291f4(System.Windows.Controls.Border)->
09229258(System.Collections.Generic.Dictionary`2[[MS.Internal.IManagedPeerBase, System.Windows],[System.Object, mscorlib]])->
092292a4(System.Collections.Generic.Dictionary`2+Entry[[MS.Internal.IManagedPeerBase, System.Windows],[System.Object, mscorlib]][])->
09228020(Telerik.Windows.Controls.RadColorSelector)->
092294c8(System.EventHandler)->
091147f4(Telerik.Windows.Controls.RadColorPicker)
For now, we can minize the issue by manually removing any RadColorPicker from our controls during Unloaded event. Please advise when this issue is resolved.