CRITICAL - watchdog._crashHandler (07:43:28.223) - Dummy-5 (12140):
NVDA crashed! Minidump written to C:\Users\andre\AppData\Local\Temp\nvda.log\..\nvda_crash.dmp
INFO - watchdog._crashHandler (07:43:30.437) - Dummy-5 (12140):
Listing stacks for Python threads:
Python stack for thread 12140 (Dummy-5):
File "watchdog.pyc", line 213, in _crashHandler
File "watchdog.pyc", line 63, in getFormattedStacksForAllThreads
Python stack for thread 4144 (virtualBuffers.MSHTML.VirtualBuffer.loadBuffer):
File "threading.pyc", line 890, in _bootstrap
File "threading.pyc", line 926, in _bootstrap_inner
File "threading.pyc", line 870, in run
File "virtualBuffers\__init__.pyc", line 444, in _loadBuffer
Python stack for thread 10748 (watchdog.CancellableCallThread.execute(<CFunctionType object at 0x05BCACD8>)):
File "threading.pyc", line 890, in _bootstrap
File "threading.pyc", line 926, in _bootstrap_inner
File "watchdog.pyc", line 332, in run
File "threading.pyc", line 552, in wait
File "threading.pyc", line 296, in wait
Python stack for thread 12044 (watchdog):
File "threading.pyc", line 890, in _bootstrap
File "threading.pyc", line 926, in _bootstrap_inner
File "threading.pyc", line 870, in run
File "watchdog.pyc", line 120, in _watcher
Python stack for thread 10612 (winInputHook):
File "threading.pyc", line 890, in _bootstrap
File "threading.pyc", line 926, in _bootstrap_inner
File "threading.pyc", line 870, in run
File "winInputHook.pyc", line 79, in hookThreadFunc
Python stack for thread 7352 (_UIAHandler.UIAHandler.MTAThread):
File "threading.pyc", line 890, in _bootstrap
File "threading.pyc", line 926, in _bootstrap_inner
File "threading.pyc", line 870, in run
File "_UIAHandler.pyc", line 315, in MTAThreadFunc
File "queue.pyc", line 170, in get
File "threading.pyc", line 296, in wait
Python stack for thread 3700 (braille._BgThread):
File "threading.pyc", line 890, in _bootstrap
File "threading.pyc", line 926, in _bootstrap_inner
File "threading.pyc", line 870, in run
File "braille.pyc", line 2187, in func
Python stack for thread 13092 (MainThread):
File "nvda.pyw", line 247, in <module>
File "core.pyc", line 568, in main
File "wx\core.pyc", line 2134, in MainLoop
File "gui\__init__.pyc", line 1062, in Notify
File "core.pyc", line 538, in run
File "queueHandler.pyc", line 88, in pumpAll
File "queueHandler.pyc", line 55, in flushQueue
File "eventHandler.pyc", line 65, in _queueEventCallback
File "eventHandler.pyc", line 241, in executeEvent
File "eventHandler.pyc", line 284, in doPreGainFocus
File "eventHandler.pyc", line 246, in executeEvent
File "eventHandler.pyc", line 96, in __init__
File "eventHandler.pyc", line 105, in next
File "NVDAObjects\__init__.pyc", line 1121, in event_focusEntered
File "speech\__init__.pyc", line 478, in speakObject
File "speech\__init__.pyc", line 517, in getObjectSpeech
File "speech\__init__.pyc", line 381, in getObjectPropertiesSpeech
File "baseObject.pyc", line 42, in __get__
File "baseObject.pyc", line 146, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyc", line 762, in _get_name
File "comtypes\__init__.pyc", line 857, in __call__
File "comtypesMonkeyPatches.pyc", line 26, in __call__
INFO - watchdog._crashHandler (07:43:30.438) - Dummy-5 (12140):
Restarting due to crash
No crash.
Reproducible with NVDA+f when quickly pressed two times in Word, Firefox, etc. And in a lot of other situations.
Bug introduced in a recent alpha build.
Steps to reproduce:
import ui;ui.browseableMessage("This is a test!", "Test")Actual behavior:
NVDA crashes with the following in the log:
Expected behavior:
No crash.
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
alpha-21359,aecff99a
Windows version:
10 Insider (64-bit) build 20251.1
Name and version of other software in use when reproducing the issue:
Reproducible with NVDA+f when quickly pressed two times in Word, Firefox, etc. And in a lot of other situations.
Other information about your system:
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
Bug introduced in a recent alpha build.
If addons are disabled, is your problem still occuring?
Yes
Did you try to run the COM registry fixing tool in NVDA menu / tools?
No