public
MainWindow()
{
AutomationManager.AutomationMode = AutomationMode.Disabled;
InitializeComponent();
}
Hello,
I investigated the scenario outlined in this item, however I was not able to reproduce the memory leak on our end. The project that I used is attached here for reference. When profiling it with a memory profiling tool (JustTrace or .NET memory profiler) I cannot observe any RadPane instances left in memory after the panes are closed. Here are the steps, which I perform on my end:
1. Start profiling the application and making sure that AutomationPeers will be created (for example by opening the Windows Virtual Keyboard).
2. Close all RadPanes in the application.
3. Force the garbage collector a few times and inspect the instances that are left via the profiling tool.
With these steps, I cannot observe RadPane objects that are not collected by the garbage collector. That is why I will proceed with closing this item.
Of course, feel free to reach out to us, if you are encountering a similar scenario and share a runnable project along with some steps, which we can follow to investigate.
Regards,
Progress Telerik