Date
1 - 11 of 11
What does this error mean?
Clarissa Mitchell
Hello NVDA users. For a little while now, I have been seeing this when
I run, particularly, Firefox with NVDA, although I can't really be sure it's Firefox that is causing the problem. But Firefox does appear to be very sluggish with NVDA. Here is the message: The window title says: NVDA helper remote injection terminate and the dialog says: error, waiting for local thread to die, already dead or not responding I notice this sometimes when I press CTRL+ALT+n to restart NVDA after it has stopped speaking for some unknown reason. I just got the NVDA update today, and it did not fix the problem. I think I first noticed this error last week. I have never encountered such an error before. |
|
Hi Clarissa,
toggle quoted message
Show quoted text
This usually means NVDA tried to perform work related to browse mode management or other operation, and somehow, things didn't work out. Usually logging out and back in fixes this. Cheers, Joseph -----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Clarissa Mitchell Sent: Monday, January 14, 2019 7:58 PM To: nvda@nvda.groups.io Subject: [nvda] What does this error mean? Hello NVDA users. For a little while now, I have been seeing this when I run, particularly, Firefox with NVDA, although I can't really be sure it's Firefox that is causing the problem. But Firefox does appear to be very sluggish with NVDA. Here is the message: The window title says: NVDA helper remote injection terminate and the dialog says: error, waiting for local thread to die, already dead or not responding I notice this sometimes when I press CTRL+ALT+n to restart NVDA after it has stopped speaking for some unknown reason. I just got the NVDA update today, and it did not fix the problem. I think I first noticed this error last week. I have never encountered such an error before. |
|
I used to get this message with an old computer.
toggle quoted message
Show quoted text
Until now, I didn't ever known what it exactly is. So I'll be looking to this thread, maybe I can finally find out what was disturbing me those days. Em 15/01/2019 01:57, Clarissa Mitchell
escreveu:
Hello NVDA users. For a little while now, I have been seeing this when I run, particularly, Firefox with NVDA, although I can't really be sure it's Firefox that is causing the problem. But Firefox does appear to be very sluggish with NVDA. Here is the message: The window title says: NVDA helper remote injection terminate and the dialog says: error, waiting for local thread to die, already dead or not responding I notice this sometimes when I press CTRL+ALT+n to restart NVDA after it has stopped speaking for some unknown reason. I just got the NVDA update today, and it did not fix the problem. I think I first noticed this error last week. I have never encountered such an error before. |
|
Hi,
toggle quoted message
Show quoted text
Technical: in some cases, NVDA relies on a DLL to perform browse mode related work. The job of this DLL is to go inside a web browser process (firefox.exe, for instance) and gather as much info about the currently open web document so NVDA can display it via its own method on the fly. Not all web browsers (and document rendering engines) will permit such an operation (Microsoft Edge is one such case), and for these, NVDA relies on API's exposed by the web browser's rendering engine( this is one of the reasons why you can't navigate to visited links quickly in Edge via first letter navigation commands, one of the visible limitations). Cheers, Jsoeph -----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee via Groups.Io Sent: Monday, January 14, 2019 8:02 PM To: nvda@nvda.groups.io Subject: Re: [nvda] What does this error mean? Hi Clarissa, This usually means NVDA tried to perform work related to browse mode management or other operation, and somehow, things didn't work out. Usually logging out and back in fixes this. Cheers, Joseph -----Original Message----- From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Clarissa Mitchell Sent: Monday, January 14, 2019 7:58 PM To: nvda@nvda.groups.io Subject: [nvda] What does this error mean? Hello NVDA users. For a little while now, I have been seeing this when I run, particularly, Firefox with NVDA, although I can't really be sure it's Firefox that is causing the problem. But Firefox does appear to be very sluggish with NVDA. Here is the message: The window title says: NVDA helper remote injection terminate and the dialog says: error, waiting for local thread to die, already dead or not responding I notice this sometimes when I press CTRL+ALT+n to restart NVDA after it has stopped speaking for some unknown reason. I just got the NVDA update today, and it did not fix the problem. I think I first noticed this error last week. I have never encountered such an error before. |
|
Annette Moore
I got that error once but I can't remember now what I was doing. I remember feeling a bit alarmed by it, though. I've not seen it again since then, though.
toggle quoted message
Show quoted text
Annette On 1/14/2019 9:57 PM, Clarissa Mitchell wrote:
Hello NVDA users. For a little while now, I have been seeing this when |
|
Brian's Mail list account
An associated issue with both Firefox and Waterfox for some time now has been sluggish page loading to the point where the whole page or part of it has server not found try again and when you do of course it loads it usually.
toggle quoted message
Show quoted text
Its not happening with no nvda I'm told, but to me this seems to point at a problem with the internet, but its obviously not that either as my machine is fast and can stream hd video with no issues. My gut feeling is as Joseph said, that at some point a link internal to the browser has to do stuff, and while its in nvda, bits of important info get lost and the browser is thus not seeing what it expects as I'd imagine it simply does not know what the dll is off doing at the time. Luckily its only a minor gripe, however it does seem less likely in Jaws. Of course having a 32 bit screenreader interacting with a 64 bit browser might well be an issue. its the sort of problem very hard to trace since I'm sure some never ever see it while others do. Brian bglists@... Sent via blueyonder. Please address personal E-mail to:- briang1@..., putting 'Brian Gaff' in the display name field. ----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@...> To: <nvda@nvda.groups.io> Sent: Tuesday, January 15, 2019 4:06 AM Subject: Re: [nvda] What does this error mean? Hi, Technical: in some cases, NVDA relies on a DLL to perform browse mode related work. The job of this DLL is to go inside a web browser process (firefox.exe, for instance) and gather as much info about the currently open web document so NVDA can display it via its own method on the fly. Not all web browsers (and document rendering engines) will permit such an operation (Microsoft Edge is one such case), and for these, NVDA relies on API's exposed by the web browser's rendering engine( this is one of the reasons why you can't navigate to visited links quickly in Edge via first letter navigation commands, one of the visible limitations). Cheers, Jsoeph -----Original Message----- From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee via Groups.Io Sent: Monday, January 14, 2019 8:02 PM To: nvda@nvda.groups.io Subject: Re: [nvda] What does this error mean? Hi Clarissa, This usually means NVDA tried to perform work related to browse mode management or other operation, and somehow, things didn't work out. Usually logging out and back in fixes this. Cheers, Joseph -----Original Message----- From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Clarissa Mitchell Sent: Monday, January 14, 2019 7:58 PM To: nvda@nvda.groups.io Subject: [nvda] What does this error mean? Hello NVDA users. For a little while now, I have been seeing this when I run, particularly, Firefox with NVDA, although I can't really be sure it's Firefox that is causing the problem. But Firefox does appear to be very sluggish with NVDA. Here is the message: The window title says: NVDA helper remote injection terminate and the dialog says: error, waiting for local thread to die, already dead or not responding I notice this sometimes when I press CTRL+ALT+n to restart NVDA after it has stopped speaking for some unknown reason. I just got the NVDA update today, and it did not fix the problem. I think I first noticed this error last week. I have never encountered such an error before. |
|
Brian's Mail list account
Its not usually fatal in any way, it just means Help I'm confused.. grin.
toggle quoted message
Show quoted text
Brian bglists@... Sent via blueyonder. Please address personal E-mail to:- briang1@..., putting 'Brian Gaff' in the display name field. ----- Original Message -----
From: "Annette Moore" <angelgirl52376@...> To: <nvda@nvda.groups.io> Sent: Tuesday, January 15, 2019 7:36 AM Subject: Re: [nvda] What does this error mean? I got that error once but I can't remember now what I was doing. I remember feeling a bit alarmed by it, though. I've not seen it again since then, though. |
|
Travis Siegel
The only time I receive this error is when I restart NVDA. I've never seen it at any other time.
toggle quoted message
Show quoted text
On 1/14/2019 11:01 PM, Joseph Lee wrote:
Hi Clarissa, |
|
zsjatoi@...
Hi,
I receive the same error message when I try to install NVDA on my laptop. I have Windows 10 Pro installed on a Dell Laptop. Moderator's note: The original post on this topic says the following: The window title says: NVDA helper remote injection terminate and the dialog says: error, waiting for local thread to die, already dead or not responding. |
|
Luke Davis
See this: https://github.com/nvaccess/nvda/issues/3944
And this: https://github.com/nvaccess/nvda/issues/9380 Post to/re-open those, if they do not lead you to a solution. Also try starting NVDA with add-ons disabled; I believe the old Focus Highlight add-on could cause this in certain circumstances, or maybe it was the actual built-in focus highlight not starting on time. You could try removing the entire Vision section from nvda.ini, if nothing else works. Luke |
|
On Sat, Nov 19, 2022 at 08:04 PM, Luke Davis wrote:
Also try starting NVDA with add-ons disabled; I believe the old Focus Highlight add-on could cause this in certain circumstances, or maybe it was the actual built-in focus highlight not starting on time.- As a side note, as someone who uses Focus Highlight, both in the Add-On version and the NVDA Core version, depending on the version of NVDA being run, I've not experienced the issue mentioned ever. I have, frequently, had the message that Focus Highlight could not load when I try to turn it on in the NVDA Core setting. That never happened with the Add-On. I agree that starting with Add-Ons disabled is something that should be tried. To the original poster, see also: The Most Basic Troubleshooting Steps for Suspected NVDA Issues -- It used to be understood that if you published and profited from a mass media platform you should also be responsible for its content. That idea is nowadays considered quaintly archaic. There is no real accountability, and almost limitless ability to post any kind of ridiculous and scurrilous nonsense. God help us. ~ Ross Goldbaum, Letter to the New York Times, Regulating Media: It’s Now Seen as a Quaint Idea, November 13, 2022 |
|