![]() ![]() After setting some breakpoints when automation events are added shows that these AutomationEvents are added via the WPF toolip popup plumbing, when there are global Win32 eventġ) Is there a way to protect my application so that UI Automation doesn't destroy its peformance? On the machine I was testing, it turned out that it was Norton Antivirus that had caused the bad interaction, but the number of programs that can trigger thisĢ) Could it be that we've somehow built our app such that we are triggering degenerate behavior when UIElementHelper.InvalidateAutomationAncestors runs? Any suggestions on how to identify something we may have done wrong? If ContextLayoutManager.From(base.Dispatcher).AutomationEvents.Count != 0. Poking around in Reflector shows that UIElement.Measure will trigger a call to InvalidateAutomationAncestors On other machines this operation is effectively instantaneous.Īttaching a debugger to the process when it is apparently hung reveals that WPF is executing deep recursive calls to UIElementHelper.InvalidateAutomationAncestors. ![]() On certain machines, expanding some expanders in our app can hang the app for minutes on end. I am dealing with a performance issue an a WPF application that is related to UI Automation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |