Re: NVDA sometimes loses control and needs to be restarted
I believe I recall this being discussed awhile ago and I think it has something to do with ways that Windows 10 communicates with NVDA. Of course, others will be able to discuss this with much more knowledge.
----- )Original Message -----
From: Lisa P Geibel
Sent: Tuesday, December 10, 2019 6:02 AM
Subject: Re: [nvda] NVDA sometimes loses control and needs to be restarted
As for me, yes, I'm using Windows 10 build 1909 and the latest stable
release of NVDA.
Lisa P. Geibel
For Mine and Marcus's Christian and Messianic audio show, call 631-403-1002 and press 9997 for that show.
For Marcus's Big Brother breaking news and shows, call the same number above, but press 9998 for that show.
For either show, once you're in, press 1, then 0
If you want to hear previous shows, after dialing the above phone number and choosing which show you want, press 2.
We'd love to hear from anyone about these shows and thank you for listening.
May YHWH bless you all
On 12/10/2019 6:38 AM, Gene wrote:
> Are those having the problem using Windows 10? I've never had it
> happen in Windows 7 or XP.
> ----- Original Message -----
> *From:* Lisa P Geibel <mailto:lisapgeibel429@...>
> *Sent:* Tuesday, December 10, 2019 5:11 AM
> *To:* email@example.com <mailto:firstname.lastname@example.org>
> *Subject:* Re: [nvda] NVDA sometimes loses control and needs to be
> Hi Vincent and others,
> SMILE I hate to break your heart, but you're not the only person this
> happens to. I was very glad to see your message and know that I'm not
> the only one it happens to. It is a fairly easy fix as you said, but can
> get to be a bother and you're right, it does seem to happen when I'm
> trying to do multiple things, but it can also happen when I'm just in
> the middle of an email. My husband thought it could be TWBlue instead of
> NVDA as that program does take a lot of resources, but I unloaded TWBlue
> and was still having problems, so I'm thinking as I first thought that
> it's something with NVDA and hopefully it will get fixed in the next
> Lisa P. Geibel
> For Mine and Marcus's Christian and Messianic audio show, call
> 631-403-1002 and press 9997 for that show.
> For Marcus's Big Brother breaking news and shows, call the same number
> above, but press 9998 for that show.
> For either show, once you're in, press 1, then 0
> If you want to hear previous shows, after dialing the above phone
> number and choosing which show you want, press 2.
> We'd love to hear from anyone about these shows and thank you for
> lisapgeibel429@... <mailto:lisapgeibel429@...>
> May YHWH bless you all
> On 12/10/2019 5:55 AM, Vincent Le Goff wrote:
> > Hi everyone,
> > 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!
> > Thanks,
> > Vincent