Articles in this section
Category / Section

How to release the memory held by AutomationPeer in WPF components?

4 mins read

Normally, the AutomationPeer support of WPF Components holds some memory and it needs to be released manually. This can be done by using the following steps.

Create a class derived from WindowAutomationPeer and override it's GetChildrenCore method and returns “null” value that clears the AutomationPeer item from memory as follows.

C#

public class FakeWindowsPeer : WindowAutomationPeer
    {
        public FakeWindowsPeer(Window window)
            : base(window)
        { }
        protected override List<AutomationPeer> GetChildrenCore()
        {
            return null;
        }
    }

Now override the OnCreateAutomationPeer of the window and it returns the class as follows.

C#

  public partial class MainWindow : Window
    {
        public MainWindow()
        {
            InitializeComponent();
        }
        protected override AutomationPeer OnCreateAutomationPeer()
        {
            return new FakeWindowsPeer(this);
        }
    }

 

Note:

This will disable automation peers.

Conclusion

I hope you enjoyed learning about how release the memory held by AutomationPeer in WPF Components.

You can refer to our WPF feature tour page to know about its other groundbreaking feature representations and documentation, and how to quickly get started for configuration specifications. 

For current customers, you can check out our components from the License and Downloads page. If you are new to Syncfusion, you can try our 30-day free trial to check out our other controls.

If you have any queries or require clarifications, please let us know in the comments section below. You can also contact us through our support forumsDirect-Trac, or feedback portal. We are always happy to assist you!

Did you find this information helpful?
Yes
No
Help us improve this page
Please provide feedback or comments
Comments (0)
Please sign in to leave a comment
Access denied
Access denied