Topics

NVDA 2018.3 beta 3 hangs after closing System Information application


Jason White
 

After using System Information on Windows 10 1803 (all up to date), and closing the application with Alt+F4, I experienced a hang in NVDA 2018.3 beta 3.

 

The log file in my local temporary directory contains the following. Please let me know whether further details are desired, or whether it has been or should be taken up in GitHub.

 

WARNING - watchdog._watcher (14:47:55.289):

Core frozen in stack:

  File "nvda.pyw", line 214, in <module>

  File "core.pyo", line 495, in main

  File "wx\core.pyo", line 2134, in MainLoop

  File "gui\__init__.pyo", line 963, in Notify

  File "core.pyo", line 466, in run

  File "queueHandler.pyo", line 83, in pumpAll

  File "queueHandler.pyo", line 50, in flushQueue

  File "eventHandler.pyo", line 62, in _queueEventCallback

  File "eventHandler.pyo", line 147, in executeEvent

  File "eventHandler.pyo", line 160, in doPreGainFocus

  File "api.pyo", line 107, in setFocusObject

  File "baseObject.pyo", line 34, in __get__

  File "baseObject.pyo", line 115, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container

  File "IAccessibleHandler.pyo", line 954, in findGroupboxObject

  File "winUser.pyo", line 430, in getClassName

 

WARNING - watchdog._watcher (14:48:10.339):

Core frozen in stack:

  File "nvda.pyw", line 214, in <module>

  File "core.pyo", line 495, in main

  File "wx\core.pyo", line 2134, in MainLoop

  File "gui\__init__.pyo", line 963, in Notify

  File "core.pyo", line 466, in run

  File "queueHandler.pyo", line 83, in pumpAll

  File "queueHandler.pyo", line 50, in flushQueue

  File "eventHandler.pyo", line 62, in _queueEventCallback

  File "eventHandler.pyo", line 147, in executeEvent

  File "eventHandler.pyo", line 160, in doPreGainFocus

  File "api.pyo", line 107, in setFocusObject

  File "baseObject.pyo", line 34, in __get__

  File "baseObject.pyo", line 115, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container

  File "IAccessibleHandler.pyo", line 945, in findGroupboxObject

  File "winUser.pyo", line 429, in getClassName

 


Quentin Christensen
 

Hi Jason,

It isn't reproducing for me, although I'm using a fast insider build of Windows here.

Two things to try:

- If you restart NVDA with add-ons disabled (press NVDA+Q then down arrow to "restart with addons disabled" and press ENTER), does it still happen?

- Particularly if the crash doesn't happen with add-ons disabled, make sure you are using the most up to date version of all your addons.  There is also an addon to check that: https://addons.nvda-project.org/addons/addonUpdater.en.html

In any case, if you could send me a copy of your full NVDA log, ideally at log level debug, I can have a closer look at what is happening.

Kind regards

Quentin.

On Tue, Sep 4, 2018 at 5:08 AM, Jason White via Groups.Io <jason@...> wrote:

After using System Information on Windows 10 1803 (all up to date), and closing the application with Alt+F4, I experienced a hang in NVDA 2018.3 beta 3.

 

The log file in my local temporary directory contains the following. Please let me know whether further details are desired, or whether it has been or should be taken up in GitHub.

 

WARNING - watchdog._watcher (14:47:55.289):

Core frozen in stack:

  File "nvda.pyw", line 214, in <module>

  File "core.pyo", line 495, in main

  File "wx\core.pyo", line 2134, in MainLoop

  File "gui\__init__.pyo", line 963, in Notify

  File "core.pyo", line 466, in run

  File "queueHandler.pyo", line 83, in pumpAll

  File "queueHandler.pyo", line 50, in flushQueue

  File "eventHandler.pyo", line 62, in _queueEventCallback

  File "eventHandler.pyo", line 147, in executeEvent

  File "eventHandler.pyo", line 160, in doPreGainFocus

  File "api.pyo", line 107, in setFocusObject

  File "baseObject.pyo", line 34, in __get__

  File "baseObject.pyo", line 115, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container

  File "IAccessibleHandler.pyo", line 954, in findGroupboxObject

  File "winUser.pyo", line 430, in getClassName

 

WARNING - watchdog._watcher (14:48:10.339):

Core frozen in stack:

  File "nvda.pyw", line 214, in <module>

  File "core.pyo", line 495, in main

  File "wx\core.pyo", line 2134, in MainLoop

  File "gui\__init__.pyo", line 963, in Notify

  File "core.pyo", line 466, in run

  File "queueHandler.pyo", line 83, in pumpAll

  File "queueHandler.pyo", line 50, in flushQueue

  File "eventHandler.pyo", line 62, in _queueEventCallback

  File "eventHandler.pyo", line 147, in executeEvent

  File "eventHandler.pyo", line 160, in doPreGainFocus

  File "api.pyo", line 107, in setFocusObject

  File "baseObject.pyo", line 34, in __get__

  File "baseObject.pyo", line 115, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container

  File "IAccessibleHandler.pyo", line 945, in findGroupboxObject

  File "winUser.pyo", line 429, in getClassName

 




--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Takuya Nishimoto
 

I have reported regarding similar issue.

https://github.com/nvaccess/nvda/issues/8434

It was difficult to reproduce on other machines than the specific environment.

--
Takuya Nishimoto
nishimotz@gmail.com

2018年9月4日(火) 4:08 Jason White via Groups.Io <jason=jasonjgw.net@groups.io>:


After using System Information on Windows 10 1803 (all up to date), and closing the application with Alt+F4, I experienced a hang in NVDA 2018.3 beta 3.



The log file in my local temporary directory contains the following. Please let me know whether further details are desired, or whether it has been or should be taken up in GitHub.



WARNING - watchdog._watcher (14:47:55.289):

Core frozen in stack:

File "nvda.pyw", line 214, in <module>

File "core.pyo", line 495, in main

File "wx\core.pyo", line 2134, in MainLoop

File "gui\__init__.pyo", line 963, in Notify

File "core.pyo", line 466, in run

File "queueHandler.pyo", line 83, in pumpAll

File "queueHandler.pyo", line 50, in flushQueue

File "eventHandler.pyo", line 62, in _queueEventCallback

File "eventHandler.pyo", line 147, in executeEvent

File "eventHandler.pyo", line 160, in doPreGainFocus

File "api.pyo", line 107, in setFocusObject

File "baseObject.pyo", line 34, in __get__

File "baseObject.pyo", line 115, in _getPropertyViaCache

File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container

File "IAccessibleHandler.pyo", line 954, in findGroupboxObject

File "winUser.pyo", line 430, in getClassName



WARNING - watchdog._watcher (14:48:10.339):

Core frozen in stack:

File "nvda.pyw", line 214, in <module>

File "core.pyo", line 495, in main

File "wx\core.pyo", line 2134, in MainLoop

File "gui\__init__.pyo", line 963, in Notify

File "core.pyo", line 466, in run

File "queueHandler.pyo", line 83, in pumpAll

File "queueHandler.pyo", line 50, in flushQueue

File "eventHandler.pyo", line 62, in _queueEventCallback

File "eventHandler.pyo", line 147, in executeEvent

File "eventHandler.pyo", line 160, in doPreGainFocus

File "api.pyo", line 107, in setFocusObject

File "baseObject.pyo", line 34, in __get__

File "baseObject.pyo", line 115, in _getPropertyViaCache

File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container

File "IAccessibleHandler.pyo", line 945, in findGroupboxObject

File "winUser.pyo", line 429, in getClassName




Quentin Christensen
 

Takuya,

Do you have any (other) addons installed, and if so, have you tried restarting with add-ons disabled?  If so, have you checked that you are using the most up to date version of any addons?

And finally, just to check, does this happen immediately after updating either NVDA or Windows, and if so, does it persist after rebooting the computer?

If you also could send me a copy of your full log, ideally at Debug level, I can have a look as well.

I forgot to mention previously, but more information on the log is available at: https://github.com/nvaccess/nvda/wiki/LogFilesAndCrashDumps


Kind regards

Quentin.





On Tue, Sep 4, 2018 at 10:01 AM, Takuya Nishimoto <nishimotz@...> wrote:
I have reported regarding similar issue.

https://github.com/nvaccess/nvda/issues/8434

It was difficult to reproduce on other machines than the specific environment.

--
Takuya Nishimoto
nishimotz@...

2018年9月4日(火) 4:08 Jason White via Groups.Io <jason=jasonjgw.net@groups.io>:
>
> After using System Information on Windows 10 1803 (all up to date), and closing the application with Alt+F4, I experienced a hang in NVDA 2018.3 beta 3.
>
>
>
> The log file in my local temporary directory contains the following. Please let me know whether further details are desired, or whether it has been or should be taken up in GitHub.
>
>
>
> WARNING - watchdog._watcher (14:47:55.289):
>
> Core frozen in stack:
>
>   File "nvda.pyw", line 214, in <module>
>
>   File "core.pyo", line 495, in main
>
>   File "wx\core.pyo", line 2134, in MainLoop
>
>   File "gui\__init__.pyo", line 963, in Notify
>
>   File "core.pyo", line 466, in run
>
>   File "queueHandler.pyo", line 83, in pumpAll
>
>   File "queueHandler.pyo", line 50, in flushQueue
>
>   File "eventHandler.pyo", line 62, in _queueEventCallback
>
>   File "eventHandler.pyo", line 147, in executeEvent
>
>   File "eventHandler.pyo", line 160, in doPreGainFocus
>
>   File "api.pyo", line 107, in setFocusObject
>
>   File "baseObject.pyo", line 34, in __get__
>
>   File "baseObject.pyo", line 115, in _getPropertyViaCache
>
>   File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container
>
>   File "IAccessibleHandler.pyo", line 954, in findGroupboxObject
>
>   File "winUser.pyo", line 430, in getClassName
>
>
>
> WARNING - watchdog._watcher (14:48:10.339):
>
> Core frozen in stack:
>
>   File "nvda.pyw", line 214, in <module>
>
>   File "core.pyo", line 495, in main
>
>   File "wx\core.pyo", line 2134, in MainLoop
>
>   File "gui\__init__.pyo", line 963, in Notify
>
>   File "core.pyo", line 466, in run
>
>   File "queueHandler.pyo", line 83, in pumpAll
>
>   File "queueHandler.pyo", line 50, in flushQueue
>
>   File "eventHandler.pyo", line 62, in _queueEventCallback
>
>   File "eventHandler.pyo", line 147, in executeEvent
>
>   File "eventHandler.pyo", line 160, in doPreGainFocus
>
>   File "api.pyo", line 107, in setFocusObject
>
>   File "baseObject.pyo", line 34, in __get__
>
>   File "baseObject.pyo", line 115, in _getPropertyViaCache
>
>   File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container
>
>   File "IAccessibleHandler.pyo", line 945, in findGroupboxObject
>
>   File "winUser.pyo", line 429, in getClassName
>
>
>
>






--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Jason White
 

Thanks – I’ll try to reproduce and to capture debug-level logs.

 

At this point, unfortunately, it will probably have to be tomorrow.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: Monday, September 3, 2018 8:01 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.3 beta 3 hangs after closing System Information application

 

Hi Jason,

 

It isn't reproducing for me, although I'm using a fast insider build of Windows here.

 

Two things to try:


- If you restart NVDA with add-ons disabled (press NVDA+Q then down arrow to "restart with addons disabled" and press ENTER), does it still happen?

 

- Particularly if the crash doesn't happen with add-ons disabled, make sure you are using the most up to date version of all your addons.  There is also an addon to check that: https://addons.nvda-project.org/addons/addonUpdater.en.html

 

In any case, if you could send me a copy of your full NVDA log, ideally at log level debug, I can have a closer look at what is happening.


Kind regards

 

Quentin.

 

On Tue, Sep 4, 2018 at 5:08 AM, Jason White via Groups.Io <jason@...> wrote:

After using System Information on Windows 10 1803 (all up to date), and closing the application with Alt+F4, I experienced a hang in NVDA 2018.3 beta 3.

 

The log file in my local temporary directory contains the following. Please let me know whether further details are desired, or whether it has been or should be taken up in GitHub.

 

WARNING - watchdog._watcher (14:47:55.289):

Core frozen in stack:

  File "nvda.pyw", line 214, in <module>

  File "core.pyo", line 495, in main

  File "wx\core.pyo", line 2134, in MainLoop

  File "gui\__init__.pyo", line 963, in Notify

  File "core.pyo", line 466, in run

  File "queueHandler.pyo", line 83, in pumpAll

  File "queueHandler.pyo", line 50, in flushQueue

  File "eventHandler.pyo", line 62, in _queueEventCallback

  File "eventHandler.pyo", line 147, in executeEvent

  File "eventHandler.pyo", line 160, in doPreGainFocus

  File "api.pyo", line 107, in setFocusObject

  File "baseObject.pyo", line 34, in __get__

  File "baseObject.pyo", line 115, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container

  File "IAccessibleHandler.pyo", line 954, in findGroupboxObject

  File "winUser.pyo", line 430, in getClassName

 

WARNING - watchdog._watcher (14:48:10.339):

Core frozen in stack:

  File "nvda.pyw", line 214, in <module>

  File "core.pyo", line 495, in main

  File "wx\core.pyo", line 2134, in MainLoop

  File "gui\__init__.pyo", line 963, in Notify

  File "core.pyo", line 466, in run

  File "queueHandler.pyo", line 83, in pumpAll

  File "queueHandler.pyo", line 50, in flushQueue

  File "eventHandler.pyo", line 62, in _queueEventCallback

  File "eventHandler.pyo", line 147, in executeEvent

  File "eventHandler.pyo", line 160, in doPreGainFocus

  File "api.pyo", line 107, in setFocusObject

  File "baseObject.pyo", line 34, in __get__

  File "baseObject.pyo", line 115, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container

  File "IAccessibleHandler.pyo", line 945, in findGroupboxObject

  File "winUser.pyo", line 429, in getClassName

 



 

--

Quentin Christensen
Training and Support Manager

 

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

 

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Don H
 

Just tried to duplicate this.  Indeed after closing the system information with alt f4 it seems that NVDA goes silent.  after the alt f4 is pressed Nvda says unknown.  Sighted help says I am back to the desktop and nothing is shown besides my normal desktop.     However if you hit windows key m speech returns.  Seems that something is open that is minimized by windows key m. 

On 9/3/2018 7:56 PM, Quentin Christensen wrote:
Takuya,

Do you have any (other) addons installed, and if so, have you tried restarting with add-ons disabled?  If so, have you checked that you are using the most up to date version of any addons?

And finally, just to check, does this happen immediately after updating either NVDA or Windows, and if so, does it persist after rebooting the computer?

If you also could send me a copy of your full log, ideally at Debug level, I can have a look as well.

I forgot to mention previously, but more information on the log is available at: https://github.com/nvaccess/nvda/wiki/LogFilesAndCrashDumps


Kind regards

Quentin.





On Tue, Sep 4, 2018 at 10:01 AM, Takuya Nishimoto <nishimotz@...> wrote:
I have reported regarding similar issue.

https://github.com/nvaccess/nvda/issues/8434

It was difficult to reproduce on other machines than the specific environment.

--
Takuya Nishimoto
nishimotz@...

2018年9月4日(火) 4:08 Jason White via Groups.Io <jason=jasonjgw.net@groups.io>:
>
> After using System Information on Windows 10 1803 (all up to date), and closing the application with Alt+F4, I experienced a hang in NVDA 2018.3 beta 3.
>
>
>
> The log file in my local temporary directory contains the following. Please let me know whether further details are desired, or whether it has been or should be taken up in GitHub.
>
>
>
> WARNING - watchdog._watcher (14:47:55.289):
>
> Core frozen in stack:
>
>   File "nvda.pyw", line 214, in <module>
>
>   File "core.pyo", line 495, in main
>
>   File "wx\core.pyo", line 2134, in MainLoop
>
>   File "gui\__init__.pyo", line 963, in Notify
>
>   File "core.pyo", line 466, in run
>
>   File "queueHandler.pyo", line 83, in pumpAll
>
>   File "queueHandler.pyo", line 50, in flushQueue
>
>   File "eventHandler.pyo", line 62, in _queueEventCallback
>
>   File "eventHandler.pyo", line 147, in executeEvent
>
>   File "eventHandler.pyo", line 160, in doPreGainFocus
>
>   File "api.pyo", line 107, in setFocusObject
>
>   File "baseObject.pyo", line 34, in __get__
>
>   File "baseObject.pyo", line 115, in _getPropertyViaCache
>
>   File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container
>
>   File "IAccessibleHandler.pyo", line 954, in findGroupboxObject
>
>   File "winUser.pyo", line 430, in getClassName
>
>
>
> WARNING - watchdog._watcher (14:48:10.339):
>
> Core frozen in stack:
>
>   File "nvda.pyw", line 214, in <module>
>
>   File "core.pyo", line 495, in main
>
>   File "wx\core.pyo", line 2134, in MainLoop
>
>   File "gui\__init__.pyo", line 963, in Notify
>
>   File "core.pyo", line 466, in run
>
>   File "queueHandler.pyo", line 83, in pumpAll
>
>   File "queueHandler.pyo", line 50, in flushQueue
>
>   File "eventHandler.pyo", line 62, in _queueEventCallback
>
>   File "eventHandler.pyo", line 147, in executeEvent
>
>   File "eventHandler.pyo", line 160, in doPreGainFocus
>
>   File "api.pyo", line 107, in setFocusObject
>
>   File "baseObject.pyo", line 34, in __get__
>
>   File "baseObject.pyo", line 115, in _getPropertyViaCache
>
>   File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container
>
>   File "IAccessibleHandler.pyo", line 945, in findGroupboxObject
>
>   File "winUser.pyo", line 429, in getClassName
>
>
>
>






--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Quentin Christensen
 

Using either 2018.3beta3, or the latest alpha, I get unknown reported as soon as I close system information, and yes, as soon as I press the windows key, or windows+m etc, I get to the start menu or desktop as expected.  I'm not getting any crash or even an error or warning like the original poster however.

I wonder if the crash is caused by the same action with a differently configured PC, or whether it is something else which is happening around the same time (an example might be changing configuration profiles if there was a triggered one for system information, or an addon which was triggered or looking for something else).



On Tue, Sep 4, 2018 at 11:42 AM, Don H <lmddh50@...> wrote:

Just tried to duplicate this.  Indeed after closing the system information with alt f4 it seems that NVDA goes silent.  after the alt f4 is pressed Nvda says unknown.  Sighted help says I am back to the desktop and nothing is shown besides my normal desktop.     However if you hit windows key m speech returns.  Seems that something is open that is minimized by windows key m. 

On 9/3/2018 7:56 PM, Quentin Christensen wrote:
Takuya,

Do you have any (other) addons installed, and if so, have you tried restarting with add-ons disabled?  If so, have you checked that you are using the most up to date version of any addons?

And finally, just to check, does this happen immediately after updating either NVDA or Windows, and if so, does it persist after rebooting the computer?

If you also could send me a copy of your full log, ideally at Debug level, I can have a look as well.

I forgot to mention previously, but more information on the log is available at: https://github.com/nvaccess/nvda/wiki/LogFilesAndCrashDumps


Kind regards

Quentin.





On Tue, Sep 4, 2018 at 10:01 AM, Takuya Nishimoto <nishimotz@...> wrote:
I have reported regarding similar issue.

https://github.com/nvaccess/nvda/issues/8434

It was difficult to reproduce on other machines than the specific environment.

--
Takuya Nishimoto
nishimotz@...

2018年9月4日(火) 4:08 Jason White via Groups.Io <jason=jasonjgw.net@groups.io>:
>
> After using System Information on Windows 10 1803 (all up to date), and closing the application with Alt+F4, I experienced a hang in NVDA 2018.3 beta 3.
>
>
>
> The log file in my local temporary directory contains the following. Please let me know whether further details are desired, or whether it has been or should be taken up in GitHub.
>
>
>
> WARNING - watchdog._watcher (14:47:55.289):
>
> Core frozen in stack:
>
>   File "nvda.pyw", line 214, in <module>
>
>   File "core.pyo", line 495, in main
>
>   File "wx\core.pyo", line 2134, in MainLoop
>
>   File "gui\__init__.pyo", line 963, in Notify
>
>   File "core.pyo", line 466, in run
>
>   File "queueHandler.pyo", line 83, in pumpAll
>
>   File "queueHandler.pyo", line 50, in flushQueue
>
>   File "eventHandler.pyo", line 62, in _queueEventCallback
>
>   File "eventHandler.pyo", line 147, in executeEvent
>
>   File "eventHandler.pyo", line 160, in doPreGainFocus
>
>   File "api.pyo", line 107, in setFocusObject
>
>   File "baseObject.pyo", line 34, in __get__
>
>   File "baseObject.pyo", line 115, in _getPropertyViaCache
>
>   File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container
>
>   File "IAccessibleHandler.pyo", line 954, in findGroupboxObject
>
>   File "winUser.pyo", line 430, in getClassName
>
>
>
> WARNING - watchdog._watcher (14:48:10.339):
>
> Core frozen in stack:
>
>   File "nvda.pyw", line 214, in <module>
>
>   File "core.pyo", line 495, in main
>
>   File "wx\core.pyo", line 2134, in MainLoop
>
>   File "gui\__init__.pyo", line 963, in Notify
>
>   File "core.pyo", line 466, in run
>
>   File "queueHandler.pyo", line 83, in pumpAll
>
>   File "queueHandler.pyo", line 50, in flushQueue
>
>   File "eventHandler.pyo", line 62, in _queueEventCallback
>
>   File "eventHandler.pyo", line 147, in executeEvent
>
>   File "eventHandler.pyo", line 160, in doPreGainFocus
>
>   File "api.pyo", line 107, in setFocusObject
>
>   File "baseObject.pyo", line 34, in __get__
>
>   File "baseObject.pyo", line 115, in _getPropertyViaCache
>
>   File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container
>
>   File "IAccessibleHandler.pyo", line 945, in findGroupboxObject
>
>   File "winUser.pyo", line 429, in getClassName
>
>
>
>






--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 




--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Gene
 

I'm not sure this is a problem.  It is very common, when I close a program that I am not actually in any program.  I may hear something when I read the title bar suchh as the name of the program I was just in or some related name.  If I go to the desktop, everything is as it should be and if I alt tab around, everything is normal with no window open that shouldn't be.  This is with Windows XP.  I use Windows 7 but not with enough use or variety of use to say if this happens in that version. 
 
Is the original problem as I described or is it that NVDA stops speaking no matter what you do and you must close and run it again?
 
Gene

----- Original message -----
From: Don H
Sent: Monday, September 03, 2018 8:42 PM
Subject: Re: [nvda] NVDA 2018.3 beta 3 hangs after closing System Information application

Just tried to duplicate this.  Indeed after closing the system information with alt f4 it seems that NVDA goes silent.  after the alt f4 is pressed Nvda says unknown.  Sighted help says I am back to the desktop and nothing is shown besides my normal desktop.     However if you hit windows key m speech returns.  Seems that something is open that is minimized by windows key m. 

On 9/3/2018 7:56 PM, Quentin Christensen wrote:
Takuya,

Do you have any (other) addons installed, and if so, have you tried restarting with add-ons disabled?  If so, have you checked that you are using the most up to date version of any addons?

And finally, just to check, does this happen immediately after updating either NVDA or Windows, and if so, does it persist after rebooting the computer?

If you also could send me a copy of your full log, ideally at Debug level, I can have a look as well.

I forgot to mention previously, but more information on the log is available at: https://github.com/nvaccess/nvda/wiki/LogFilesAndCrashDumps


Kind regards

Quentin.





On Tue, Sep 4, 2018 at 10:01 AM, Takuya Nishimoto <nishimotz@...> wrote:
I have reported regarding similar issue.

https://github.com/nvaccess/nvda/issues/8434

It was difficult to reproduce on other machines than the specific environment.

--
Takuya Nishimoto
nishimotz@...

2018年9月4日(火) 4:08 Jason White via Groups.Io <jason=jasonjgw.net@groups.io>:
>
> After using System Information on Windows 10 1803 (all up to date), and closing the application with Alt+F4, I experienced a hang in NVDA 2018.3 beta 3.
>
>
>
> The log file in my local temporary directory contains the following. Please let me know whether further details are desired, or whether it has been or should be taken up in GitHub.
>
>
>
> WARNING - watchdog._watcher (14:47:55.289):
>
> Core frozen in stack:
>
>   File "nvda.pyw", line 214, in <module>
>
>   File "core.pyo", line 495, in main
>
>   File "wx\core.pyo", line 2134, in MainLoop
>
>   File "gui\__init__.pyo", line 963, in Notify
>
>   File "core.pyo", line 466, in run
>
>   File "queueHandler.pyo", line 83, in pumpAll
>
>   File "queueHandler.pyo", line 50, in flushQueue
>
>   File "eventHandler.pyo", line 62, in _queueEventCallback
>
>   File "eventHandler.pyo", line 147, in executeEvent
>
>   File "eventHandler.pyo", line 160, in doPreGainFocus
>
>   File "api.pyo", line 107, in setFocusObject
>
>   File "baseObject.pyo", line 34, in __get__
>
>   File "baseObject.pyo", line 115, in _getPropertyViaCache
>
>   File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container
>
>   File "IAccessibleHandler.pyo", line 954, in findGroupboxObject
>
>   File "winUser.pyo", line 430, in getClassName
>
>
>
> WARNING - watchdog._watcher (14:48:10.339):
>
> Core frozen in stack:
>
>   File "nvda.pyw", line 214, in <module>
>
>   File "core.pyo", line 495, in main
>
>   File "wx\core.pyo", line 2134, in MainLoop
>
>   File "gui\__init__.pyo", line 963, in Notify
>
>   File "core.pyo", line 466, in run
>
>   File "queueHandler.pyo", line 83, in pumpAll
>
>   File "queueHandler.pyo", line 50, in flushQueue
>
>   File "eventHandler.pyo", line 62, in _queueEventCallback
>
>   File "eventHandler.pyo", line 147, in executeEvent
>
>   File "eventHandler.pyo", line 160, in doPreGainFocus
>
>   File "api.pyo", line 107, in setFocusObject
>
>   File "baseObject.pyo", line 34, in __get__
>
>   File "baseObject.pyo", line 115, in _getPropertyViaCache
>
>   File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container
>
>   File "IAccessibleHandler.pyo", line 945, in findGroupboxObject
>
>   File "winUser.pyo", line 429, in getClassName
>
>
>
>






--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Brian's Mail list account <bglists@...>
 

Well I often see a similar effect if I close Word, but the freeze is less than five seconds normally, and yes its always been around on xp and 7. Even on fast machines so I'm thinking it might be bit of a red herring. I can look at a log and find quite a few core frozen in stack items, but often they are so fleeting that if they cause any problem, it might be no reading of a web page or no indication of where you are, ie unknown, and you can usually recover it by making things refresh.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Gene" <gsasner@ripco.com>
To: <nvda@nvda.groups.io>
Sent: Tuesday, September 04, 2018 4:28 AM
Subject: Re: [nvda] NVDA 2018.3 beta 3 hangs after closing System Information application


I'm not sure this is a problem. It is very common, when I close a program that I am not actually in any program. I may hear something when I read the title bar suchh as the name of the program I was just in or some related name. If I go to the desktop, everything is as it should be and if I alt tab around, everything is normal with no window open that shouldn't be. This is with Windows XP. I use Windows 7 but not with enough use or variety of use to say if this happens in that version.

Is the original problem as I described or is it that NVDA stops speaking no matter what you do and you must close and run it again?

Gene
----- Original message -----

From: Don H
Sent: Monday, September 03, 2018 8:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.3 beta 3 hangs after closing System Information application


Just tried to duplicate this. Indeed after closing the system information with alt f4 it seems that NVDA goes silent. after the alt f4 is pressed Nvda says unknown. Sighted help says I am back to the desktop and nothing is shown besides my normal desktop. However if you hit windows key m speech returns. Seems that something is open that is minimized by windows key m.


On 9/3/2018 7:56 PM, Quentin Christensen wrote:

Takuya,


Do you have any (other) addons installed, and if so, have you tried restarting with add-ons disabled? If so, have you checked that you are using the most up to date version of any addons?


And finally, just to check, does this happen immediately after updating either NVDA or Windows, and if so, does it persist after rebooting the computer?


If you also could send me a copy of your full log, ideally at Debug level, I can have a look as well.

I forgot to mention previously, but more information on the log is available at: https://github.com/nvaccess/nvda/wiki/LogFilesAndCrashDumps




Kind regards


Quentin.










On Tue, Sep 4, 2018 at 10:01 AM, Takuya Nishimoto <nishimotz@gmail.com> wrote:

I have reported regarding similar issue.

https://github.com/nvaccess/nvda/issues/8434

It was difficult to reproduce on other machines than the specific environment.

--
Takuya Nishimoto
nishimotz@gmail.com

2018年9月4日(火) 4:08 Jason White via Groups.Io <jason=jasonjgw.net@groups.io>:

>
> After using System Information on Windows 10 1803 (all up to date), and closing the application with Alt+F4, I experienced a hang in NVDA 2018.3 beta 3.
>
>
>
> The log file in my local temporary directory contains the following. Please let me know whether further details are desired, or whether it has been or should be taken up in GitHub.
>
>
>
> WARNING - watchdog._watcher (14:47:55.289):
>
> Core frozen in stack:
>
> File "nvda.pyw", line 214, in <module>
>
> File "core.pyo", line 495, in main
>
> File "wx\core.pyo", line 2134, in MainLoop
>
> File "gui\__init__.pyo", line 963, in Notify
>
> File "core.pyo", line 466, in run
>
> File "queueHandler.pyo", line 83, in pumpAll
>
> File "queueHandler.pyo", line 50, in flushQueue
>
> File "eventHandler.pyo", line 62, in _queueEventCallback
>
> File "eventHandler.pyo", line 147, in executeEvent
>
> File "eventHandler.pyo", line 160, in doPreGainFocus
>
> File "api.pyo", line 107, in setFocusObject
>
> File "baseObject.pyo", line 34, in __get__
>
> File "baseObject.pyo", line 115, in _getPropertyViaCache
>
> File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container
>
> File "IAccessibleHandler.pyo", line 954, in findGroupboxObject
>
> File "winUser.pyo", line 430, in getClassName
>
>
>
> WARNING - watchdog._watcher (14:48:10.339):
>
> Core frozen in stack:
>
> File "nvda.pyw", line 214, in <module>
>
> File "core.pyo", line 495, in main
>
> File "wx\core.pyo", line 2134, in MainLoop
>
> File "gui\__init__.pyo", line 963, in Notify
>
> File "core.pyo", line 466, in run
>
> File "queueHandler.pyo", line 83, in pumpAll
>
> File "queueHandler.pyo", line 50, in flushQueue
>
> File "eventHandler.pyo", line 62, in _queueEventCallback
>
> File "eventHandler.pyo", line 147, in executeEvent
>
> File "eventHandler.pyo", line 160, in doPreGainFocus
>
> File "api.pyo", line 107, in setFocusObject
>
> File "baseObject.pyo", line 34, in __get__
>
> File "baseObject.pyo", line 115, in _getPropertyViaCache
>
> File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container
>
> File "IAccessibleHandler.pyo", line 945, in findGroupboxObject
>
> File "winUser.pyo", line 429, in getClassName
>
>
>
>










--

Quentin Christensen
Training and Support Manager


Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/


www.nvaccess.org

Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess


Jason White
 

In this case, pressing Alt+tab to try to switch to any of the open windows didn't work for me. I can't remember what else I tried.

I'll set aside some time and attempt to reproduce.

On 9/4/18, 08:37, "Brian's Mail list account via Groups.Io" <nvda@nvda.groups.io on behalf of bglists=blueyonder.co.uk@groups.io> wrote:

Well I often see a similar effect if I close Word, but the freeze is less
than five seconds normally, and yes its always been around on xp and 7. Even
on fast machines so I'm thinking it might be bit of a red herring. I can
look at a log and find quite a few core frozen in stack items, but often
they are so fleeting that if they cause any problem, it might be no reading
of a web page or no indication of where you are, ie unknown, and you can
usually recover it by making things refresh.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Gene" <gsasner@ripco.com>
To: <nvda@nvda.groups.io>
Sent: Tuesday, September 04, 2018 4:28 AM
Subject: Re: [nvda] NVDA 2018.3 beta 3 hangs after closing System
Information application


I'm not sure this is a problem. It is very common, when I close a program
that I am not actually in any program. I may hear something when I read the
title bar suchh as the name of the program I was just in or some related
name. If I go to the desktop, everything is as it should be and if I alt
tab around, everything is normal with no window open that shouldn't be.
This is with Windows XP. I use Windows 7 but not with enough use or variety
of use to say if this happens in that version.

Is the original problem as I described or is it that NVDA stops speaking no
matter what you do and you must close and run it again?

Gene
----- Original message -----

From: Don H
Sent: Monday, September 03, 2018 8:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.3 beta 3 hangs after closing System
Information application


Just tried to duplicate this. Indeed after closing the system information
with alt f4 it seems that NVDA goes silent. after the alt f4 is pressed
Nvda says unknown. Sighted help says I am back to the desktop and nothing
is shown besides my normal desktop. However if you hit windows key m
speech returns. Seems that something is open that is minimized by windows
key m.


On 9/3/2018 7:56 PM, Quentin Christensen wrote:

Takuya,


Do you have any (other) addons installed, and if so, have you tried
restarting with add-ons disabled? If so, have you checked that you are
using the most up to date version of any addons?


And finally, just to check, does this happen immediately after updating
either NVDA or Windows, and if so, does it persist after rebooting the
computer?


If you also could send me a copy of your full log, ideally at Debug level,
I can have a look as well.

I forgot to mention previously, but more information on the log is
available at: https://github.com/nvaccess/nvda/wiki/LogFilesAndCrashDumps




Kind regards


Quentin.










On Tue, Sep 4, 2018 at 10:01 AM, Takuya Nishimoto <nishimotz@gmail.com>
wrote:

I have reported regarding similar issue.

https://github.com/nvaccess/nvda/issues/8434

It was difficult to reproduce on other machines than the specific
environment.

--
Takuya Nishimoto
nishimotz@gmail.com

2018年9月4日(火) 4:08 Jason White via Groups.Io
<jason=jasonjgw.net@groups.io>:

>
> After using System Information on Windows 10 1803 (all up to date),
and closing the application with Alt+F4, I experienced a hang in NVDA 2018.3
beta 3.
>
>
>
> The log file in my local temporary directory contains the following.
Please let me know whether further details are desired, or whether it has
been or should be taken up in GitHub.
>
>
>
> WARNING - watchdog._watcher (14:47:55.289):
>
> Core frozen in stack:
>
> File "nvda.pyw", line 214, in <module>
>
> File "core.pyo", line 495, in main
>
> File "wx\core.pyo", line 2134, in MainLoop
>
> File "gui\__init__.pyo", line 963, in Notify
>
> File "core.pyo", line 466, in run
>
> File "queueHandler.pyo", line 83, in pumpAll
>
> File "queueHandler.pyo", line 50, in flushQueue
>
> File "eventHandler.pyo", line 62, in _queueEventCallback
>
> File "eventHandler.pyo", line 147, in executeEvent
>
> File "eventHandler.pyo", line 160, in doPreGainFocus
>
> File "api.pyo", line 107, in setFocusObject
>
> File "baseObject.pyo", line 34, in __get__
>
> File "baseObject.pyo", line 115, in _getPropertyViaCache
>
> File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in
_get_container
>
> File "IAccessibleHandler.pyo", line 954, in findGroupboxObject
>
> File "winUser.pyo", line 430, in getClassName
>
>
>
> WARNING - watchdog._watcher (14:48:10.339):
>
> Core frozen in stack:
>
> File "nvda.pyw", line 214, in <module>
>
> File "core.pyo", line 495, in main
>
> File "wx\core.pyo", line 2134, in MainLoop
>
> File "gui\__init__.pyo", line 963, in Notify
>
> File "core.pyo", line 466, in run
>
> File "queueHandler.pyo", line 83, in pumpAll
>
> File "queueHandler.pyo", line 50, in flushQueue
>
> File "eventHandler.pyo", line 62, in _queueEventCallback
>
> File "eventHandler.pyo", line 147, in executeEvent
>
> File "eventHandler.pyo", line 160, in doPreGainFocus
>
> File "api.pyo", line 107, in setFocusObject
>
> File "baseObject.pyo", line 34, in __get__
>
> File "baseObject.pyo", line 115, in _getPropertyViaCache
>
> File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in
_get_container
>
> File "IAccessibleHandler.pyo", line 945, in findGroupboxObject
>
> File "winUser.pyo", line 429, in getClassName
>
>
>
>










--

Quentin Christensen
Training and Support Manager


Official NVDA Training modules and expert certification now available:
http://www.nvaccess.org/shop/


www.nvaccess.org

Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess


Jason White
 

By way of update, I haven't yet been able to reproduce this with add-ons disabled.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Jason White via Groups.Io
Sent: Tuesday, September 4, 2018 7:48 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.3 beta 3 hangs after closing System Information application

In this case, pressing Alt+tab to try to switch to any of the open windows didn't work for me. I can't remember what else I tried.

I'll set aside some time and attempt to reproduce.

On 9/4/18, 08:37, "Brian's Mail list account via Groups.Io" <nvda@nvda.groups.io on behalf of bglists=blueyonder.co.uk@groups.io> wrote:

Well I often see a similar effect if I close Word, but the freeze is less
than five seconds normally, and yes its always been around on xp and 7. Even
on fast machines so I'm thinking it might be bit of a red herring. I can
look at a log and find quite a few core frozen in stack items, but often
they are so fleeting that if they cause any problem, it might be no reading
of a web page or no indication of where you are, ie unknown, and you can
usually recover it by making things refresh.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Gene" <gsasner@ripco.com>
To: <nvda@nvda.groups.io>
Sent: Tuesday, September 04, 2018 4:28 AM
Subject: Re: [nvda] NVDA 2018.3 beta 3 hangs after closing System
Information application


I'm not sure this is a problem. It is very common, when I close a program
that I am not actually in any program. I may hear something when I read the
title bar suchh as the name of the program I was just in or some related
name. If I go to the desktop, everything is as it should be and if I alt
tab around, everything is normal with no window open that shouldn't be.
This is with Windows XP. I use Windows 7 but not with enough use or variety
of use to say if this happens in that version.

Is the original problem as I described or is it that NVDA stops speaking no
matter what you do and you must close and run it again?

Gene
----- Original message -----

From: Don H
Sent: Monday, September 03, 2018 8:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.3 beta 3 hangs after closing System
Information application


Just tried to duplicate this. Indeed after closing the system information
with alt f4 it seems that NVDA goes silent. after the alt f4 is pressed
Nvda says unknown. Sighted help says I am back to the desktop and nothing
is shown besides my normal desktop. However if you hit windows key m
speech returns. Seems that something is open that is minimized by windows
key m.


On 9/3/2018 7:56 PM, Quentin Christensen wrote:

Takuya,


Do you have any (other) addons installed, and if so, have you tried
restarting with add-ons disabled? If so, have you checked that you are
using the most up to date version of any addons?


And finally, just to check, does this happen immediately after updating
either NVDA or Windows, and if so, does it persist after rebooting the
computer?


If you also could send me a copy of your full log, ideally at Debug level,
I can have a look as well.

I forgot to mention previously, but more information on the log is
available at: https://github.com/nvaccess/nvda/wiki/LogFilesAndCrashDumps




Kind regards


Quentin.










On Tue, Sep 4, 2018 at 10:01 AM, Takuya Nishimoto <nishimotz@gmail.com>
wrote:

I have reported regarding similar issue.

https://github.com/nvaccess/nvda/issues/8434

It was difficult to reproduce on other machines than the specific
environment.

--
Takuya Nishimoto
nishimotz@gmail.com

2018年9月4日(火) 4:08 Jason White via Groups.Io
<jason=jasonjgw.net@groups.io>:

>
> After using System Information on Windows 10 1803 (all up to date),
and closing the application with Alt+F4, I experienced a hang in NVDA 2018.3
beta 3.
>
>
>
> The log file in my local temporary directory contains the following.
Please let me know whether further details are desired, or whether it has
been or should be taken up in GitHub.
>
>
>
> WARNING - watchdog._watcher (14:47:55.289):
>
> Core frozen in stack:
>
> File "nvda.pyw", line 214, in <module>
>
> File "core.pyo", line 495, in main
>
> File "wx\core.pyo", line 2134, in MainLoop
>
> File "gui\__init__.pyo", line 963, in Notify
>
> File "core.pyo", line 466, in run
>
> File "queueHandler.pyo", line 83, in pumpAll
>
> File "queueHandler.pyo", line 50, in flushQueue
>
> File "eventHandler.pyo", line 62, in _queueEventCallback
>
> File "eventHandler.pyo", line 147, in executeEvent
>
> File "eventHandler.pyo", line 160, in doPreGainFocus
>
> File "api.pyo", line 107, in setFocusObject
>
> File "baseObject.pyo", line 34, in __get__
>
> File "baseObject.pyo", line 115, in _getPropertyViaCache
>
> File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in
_get_container
>
> File "IAccessibleHandler.pyo", line 954, in findGroupboxObject
>
> File "winUser.pyo", line 430, in getClassName
>
>
>
> WARNING - watchdog._watcher (14:48:10.339):
>
> Core frozen in stack:
>
> File "nvda.pyw", line 214, in <module>
>
> File "core.pyo", line 495, in main
>
> File "wx\core.pyo", line 2134, in MainLoop
>
> File "gui\__init__.pyo", line 963, in Notify
>
> File "core.pyo", line 466, in run
>
> File "queueHandler.pyo", line 83, in pumpAll
>
> File "queueHandler.pyo", line 50, in flushQueue
>
> File "eventHandler.pyo", line 62, in _queueEventCallback
>
> File "eventHandler.pyo", line 147, in executeEvent
>
> File "eventHandler.pyo", line 160, in doPreGainFocus
>
> File "api.pyo", line 107, in setFocusObject
>
> File "baseObject.pyo", line 34, in __get__
>
> File "baseObject.pyo", line 115, in _getPropertyViaCache
>
> File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in
_get_container
>
> File "IAccessibleHandler.pyo", line 945, in findGroupboxObject
>
> File "winUser.pyo", line 429, in getClassName
>
>
>
>










--

Quentin Christensen
Training and Support Manager


Official NVDA Training modules and expert certification now available:
http://www.nvaccess.org/shop/


www.nvaccess.org

Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess