Yes, something along these lines appears to be happening. With old
toggle quoted messageShow quoted text
Office apps I can sort of understand why it might be the case, as
there are ancient COM interfaces being used, and these might force a
process to stay running as long as they are not released by the
client. But why my development environment, which doesn't get any
special treatment from NVDA?
Let's gather data on this by periodically closing everything and
checking which processes are still present, then restarting NVDA to
see how many of them this gets rid of. Once fixed, this might improve
Am Do., 23. Aug. 2018 um 10:18 Uhr schrieb Brian's Mail list account
via Groups.Io <bglists@...>:
Hmm, I've seen this with other office bits as well, like Access runtime for
Maybe its still hooked into the code of these older applications making
windows unable to close them due to this.
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Felix G." <constantlyvariable@...>
Sent: Wednesday, August 22, 2018 1:19 PM
Subject: [nvda] NVDA keeping another process open
Has anyone else noticed that when NVDA is running, it seems to keep
some other processes permanently open? For example, there is a
development environment, let's call it x, which I use for creating a
software component. Strangely, when I open x and then close it again,
it stays running as a process in task manager, but as soon as I close
NVDA it also closes. I've tried with two other screen readers and they
don't affect it in this way, that is, with those running, the process
stops immediately when I close its window. So NVDA seems to do
something to certain other processes which keeps them from
I noticed the same with Outlook 2007, by the way, which I am still
using on one machine. That also won't close as long as NVDA is
running, but as soon as I exit NVDA, Outlook closes along with it.
Other screen readers don't affect Outlook in this way.