Re: NVDA sometimes loses control and needs to be restarted
That may not be the same problem, since evidently, others can unload NVDA and load it again. I suspect that your keyboard may stop responding.
My one experience with one computer where this happens can't be generalized, but I have one desktop where the keyboard stops communicating with the machine sometimes. I can unplug and reconnect the keyboard and that usually corrects the problem. Your machine is evidently a laptop so you can't do that, of course.
I don't use Windows 10 so I won't describe the procedure, but you might find it easier and faster to set the on/off button to reboot when you press it for a moment and release it, if there is such an option.
----- Original Message -----
Hi ☺ This occasionally happens to me as well. It's as if the keyboard stops responding. When this occurs I use the touchscreen to reboot the machine and the problem goes away.
From: email@example.com <firstname.lastname@example.org> On Behalf Of Vincent Le Goff
Sent: Tuesday, December 10, 2019 5:55 AM
Subject: [nvda] NVDA sometimes loses control and needs to be restarted
This has been happening for some time, on so many computers and with so many different NVDA versions I can't believe I would be the only one to see this, and it's not a huge inconvenience, but it's strange and might be worth looking into. Regardless of the activity sometimes NVDA "loses control". The key hooks (the NVDA key and all the shortcuts associated with it) stop working. Using the numeric keypad works as would without NVDA. Pressing Caplocks, which is a NVDA key for me, triggers the CapLock function. NVDA still works somewhat and tries to report information, but one can't open the NVDA menu, read the time, look at the window title or indeed do lots of things controlled directly by NVDA.
When does it happen? I've tried to reproduce the issue and it's tricky. It never seems to happen at a given time or in any given application. All I know is that it seems to "lose control" when a lot of memory is required by other applications, which creates some kind of lag. So this happens in a browser when the site has a lot of scripts for instance. This can happen in Word if the document is long. This can happen while the Windows CLI is opened and a "demanding" task is running. This can happen when lots of update information is sent to NVDA (the message queue gets long). It happens more frequently if the machine on which NVDA runs doesn't have a lot of memory. It sounds like a Windows lock, not NVDA's fault, but is there a workaround? Restarting NVDA and the delay it causes isn't really annoying, but it's definitely strange.
Most important question though: has anyone noticed this problem? Or am I the only lucky one? Does happen!