Possible Memory Retention Issue with SyntaxEditor and Automation Peers

Unfortunately, this appears to be an issue with how WPF is implemented, so we don't have any specific recommendations related to SyntaxEditor.  It does at least appear that the memory will eventually be recovered, even if it is not as quickly as one might hope.

It appears the only way to "resolve" this is to effectively disable UI automation by creating a custom AutomationPeer for each control that essentially does nothing.  Even if it was possible to track down and replace each AutomationPeer used by our controls, this is not something we would recommend since it also means the controls will stop working with screen readers and other accessibility software.

Understood. It's a bit unfortunate, but I suppose there's not much we can do on our end aside from possibly opening an issue in the WPF repository.

Out of curiosity (since we don’t want to disable UI automation), is it possible for us to disable it ourselves externally, or is it something that's handled internally within the controls?

Thanks again for the clarification.

Sorry, but I'm not entirely clear on what you are trying to disable when you say "disable it oursevles" since you also said you don't want to disable UI automation.  Each AutomationPeer class is what enables UI automation to work, and every control has a default AutomationPeer.  I am not aware of any type of global setting to disable the creation of AutomationPeer classes since they are essential to UI automation and accessibility APIs.