Has anyone else seen this? Partner @RainbowRemedy is having this strange bug with #NVDA and Chrome. Whenever she alt tabs out of chrome, NVDA just hangs, sometimes completely. Working inside of chrome is fine, and as I understand it, sometimes it will recover after a few seconds and it behaves fine on the rest of the system. She's on NVDA 2025.1, but this was happening on 2024 as well. Have checked after getting rid of any add-ons that might get involved with browsers. Haven't yet checked with all add-ons disabled to my knowledge, but unsure if that would make any difference, the list is rather short, but includes IBMTTS which she needs to be able to use it really. Has anyone else seen this and knows of a fix for it? Windows 10. Will not accept "don't use chrome" as an answer. #NVDASR #blind
in reply to Jamie Teh

@jcsteh This is the fic I was reading recently. It's 903 KB so less than a meg, and it would take a few seconds, sometimes longer, to re-find it's place. Try:
1. Opening the document.
2. Going to the last chapter, which is easy because they're all in headings.
3. Windows D it out of the way, then alt-tab back. See if it lags for you.

dropbox.com/scl/fi/fcdn21f6ceb…

in reply to aaron

@fireborn Do you have easy table navigator installed? It's not 100% consistent given she wasn't on huge pages, but seems to have gone away after, when she went to prune more add-ons to try and narrow the problem, she pruned easy table navigator. If so, that is bizarre, as while that does interact with virtual buffers I didn't think that would cause something like that, surely it doesn't have to search the entire page for tables or something?
in reply to x0

Follow-up: It seems the behavior has either changed or there was a miscommunication initially. It happens when she alt tabs back into chrome. I've gotten her to send me a debug log, and the watchdog notes no freeze at all. Instead, it's as if the window never gains focus. She presses arrows and tab and no response happens. When she then goes to restart NVDA, as shutdown is commencing, the log spits this out, unsure if it's related.
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._getIA2RelationFirstTarget (18:17:25.207) - MainThread (13420):
Unable to use _getIA2TargetsForRelationsOfType, fallback to _IA2Relations.
DEBUG - NVDAObjects.IAccessible.IAccessible._get__IA2Relations (18:17:25.207) - MainThread (13420):
Not an IA2.IAccessible2
DEBUG - NVDAObjects.IAccessible.IAccessible._getIA2RelationFirstTarget (18:17:25.207) - MainThread (13420):
Unable to fetch _IA2Relations
Traceback (most recent call last):
File "NVDAObjects\IAccessible\__init__.pyc", line 1908, in _getIA2RelationFirstTarget
File "baseObject.pyc", line 59, in __get__
File "baseObject.pyc", line 167, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyc", line 1827, in _get__IA2Relations
NotImplementedError
I've since tried having her turn off the setting in advanced settings for using UIA to access edge and other chromium browsers when available. it was previously set to default (only when necessary), we've now set it to no and she hasn't reported it doing it again. Whereas before, this wasn't completely random, it was easily repeatable after NVDA had been restarted and alt tabbing into chrome. I think she was on the chat GPT website in this case? Which is definitely not big enough of a page to lag out the buffer.
@RainbowRemedy CC @jcsteh