Hi pv Upendran,
Debugging memory leaks is often not trivial, but there are ways to do so.
If you think that an object should be collected, you can always force garbage collection by calling the
Then, there should be no "strong" references to the control you want to dispose of. If you suspect that a part of your application may be leaking, you can use tools like WinDbg to check whether an object is still in memory and if it is, what references are keeping it there.
Generally, you should not keep strong references of controls in your ViewModel. You can always use WeakReference fields that are wrapped in a typed property.
We are not aware of a memory leak in the TabControl, but we will be happy to investigate if you want.
All the best,
the Telerik team