Re: office 2019 word and nvda


 

Hi all,
Based on the log posted by Luke, it appears NVDA is trying to obtain
information from a control that no longer exists (according to accessibility
API's) or something is grabbing NVDA's attention too long.
Technical: I think there is a thread deadlock somewhere. The log fragment in
question (see the GitHub issue Luke created) mostly points to threads trying
to wait for something from its processing queue. This is evidenced by the
fact that multiple threads are waiting for a response from a "dead" UIA
element in regards to supported properties.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Luke Davis
Sent: Thursday, July 16, 2020 1:43 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] office 2019 word and nvda

I have created an issue for this. If it is happening to you and you want it
fixed, please post a comment and possibly more information on this issue:

https://github.com/nvaccess/nvda/issues/11391

Luke

Join nvda@nvda.groups.io to automatically receive all group messages.