UIA performance/WinDbg: slow response when pressing Alt+Tab after pressing Control+D from WinDbg

[josephsl]

Hi,

Reported by @tspivey via Skype: UIA responds slowly when pressing Alt+Tab from WinDbg.

Steps to reproduce:

1. Install Windows SDK.
2. Open WinDbg (any version will do).
3. With WinDbg open, press Control+D to open crash dumps.
4. Press Alt+Tab.

Actual behavior:

Switching between apps is very slow.

Expected behavior:

Switching between apps is snappy.

System configuration:

NVDA Installed/portable/running from source:

Installed

NVDA version:

2018.2.1 and alpha.15634

Windows version:

Windows 10 versions 1803 and Insider Preview

Name and version of other software in use when reproducing the issue:

WinDbg

Other information about your system:

@tspivey uses version 1803, while I use Insider Preview.

Other questions:

Does the issue still occur after restarting your PC?

Yes

Have you tried any other versions of NVDA?

No

Technical:

Possibly caused by WinDbg itself.

Workarounds:

For Version 1803 (build 17134), remove UIA name and value properties from properties to event ID's dictionary in UIA handler. This resolves this, although it raises the question as to which window is causing performance issues when firing name change and/or value change events.

In Insider Preview, use IUIAutomation6::CoalesceEvents (RS5, the flag must be set to 1/enabled).

Thanks.

[Adriani90]

@josephsl is this issue still reproducible? There are to PRs merged related to this and I guess there were changes between Windows 10 1803 and las build in 1809.

[josephsl]

Hi, the person you should talk to would be @tspivey, as he is the one who have tested this fix, too. Thanks. From: Adriani90 <notifications@github.com> Sent: Saturday, January 12, 2019 4:46 AM To: nvaccess/nvda <nvda@noreply.github.com> Cc: Joseph Lee <joseph.lee22590@gmail.com>; Mention <mention@noreply.github.com> Subject: Re: [nvaccess/nvda] UIA performance/WinDbg: slow response when pressing Alt+Tab after pressing Control+D from WinDbg (#8535) @josephsl <https://github.com/josephsl> is this issue still reproducible? There are to PRs merged related to this and I guess there were changes between Windows 10 1803 and las build in 1809. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#8535 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgLkGKLs4oXlXCZC2gwFqVUOqBJOnOrks5vCdkNgaJpZM4VaM3N> .

[Adriani90]

@@tspivey are you still having this issue? Or should we close it?

[Adriani90]

No updates so far from the person who can reproduce it. I am closing this issue as abandoned. Please comment on it if you still have this issue and we can reopen it. Thanks.