Understanding Threading Issues
This topic describes common threading scenarios for Microsoft UI Automation client implementations and explains how to avoid problems that can occur if a client uses threading incorrectly.
This topic contains the following sections:
- UI Automation and the UI Thread
- Threading Model for Event Handlers
- COM Apartment Affinity on 64-bit Windows
- Related topics
Because of the way UI Automation uses Windows messages, conflicts can occur when a client application attempts to interact with its own UI on the UI thread. These conflicts can lead to very slow performance, or even cause the application to stop responding.
If your client application is intended to interact with all elements on the desktop, including its own UI, you should make all UI Automation calls from a separate thread. This includes locating elements, for example, by using IUIAutomationTreeWalker or the IUIAutomationElement::FindAll method and using control patterns. This thread should not own any windows, and should be a Component Object Model (COM) Multithreaded Apartment (MTA) model thread (one that initializes COM by calling CoInitializeEx with the COINIT_MULTITHREADED flag.)
It is safe to make UI Automation calls in a UI Automation event handler, because the event handler is always called on a non-UI thread. However, when subscribing to events that may originate from your client application UI, you must make the call to IUIAutomation::AddAutomationEventHandler, or a related method, on a non-UI thread (which should also be an MTA thread). Remove event handlers on the same thread.
A UI Automation client should not use multiple threads to add or remove event handlers. Unexpected behavior can result if one event handler is being added or removed while another is being added or removed in the same client process.
A UI Automation client should use the COM MTA threading model for threads that implement event handlers. Using the Single-threaded Apartment (STA) model can cause problems such as preventing clients from removing event handlers from the thread.
According to the COM specification, the lifetime of a remote object is governed by the lifetime of the apartment where the CoCreateInstance function is called to create the object. When the original apartment shuts down, the remote object is also released.
For UI Automation clients, this COM behavior can mean that the lifetime of the remote 32/64 helper (created by UIAutomationCore.dll) used by a 32-bit element is governed by the apartment lifetime of the thread that created the element. If the UI Automation client marshals the element to another thread, the element can become invalidated when the originating apartment shuts down. The UI Automation client should handle these issues gracefully by catching errors while using marshaled automation elements.
The same issue can occur with a 32-bit UI Automation client that has 64-bit elements.
- Obtaining UI Automation Elements
- Subscribing to UI Automation Events
- UI Automation Events Overview
- Other Resources
- INFO: Descriptions and Workings of OLE Threading Models