Steps to reproduce
Open a a fairly large Microsoft Word document.
Switch to browse mode by pressing NVDA+Space.
Try a slightly intensive document reading command such as initiating a say all.
Now, immediately press NVDA+F1 to open the Log Viewer.
Expected Result: The Log Viewer should open without any hitch and NVDA should report it.
Actual Result: There is a significant freeze during this time, and NVDA takes a while to respond and announce the opening of the Log Viewer and begin reading its contents despite having issued necessary reading commands already.
Test Environment
Microsoft Office Word 2010
NVDA version 2016.3
Document of 84 pages (more or less pages should be able to demonstrate this problem consistently as well)
In my observation, NVDA functions very slowly and unresponsively in Microsoft Word's browse mode. Since I usually deal with school textbooks which span up to a few hundreds of pages, and sometimes toggle browse mode to use NVDA's additional functionalities in that state, I have constantly marked this delay. It It is my belief that the freeze that I am describing relates more to a flawed or problematic Word browse mode implementation as opposed to deficiencies in the Log Viewer.
In any case, here is a snippet of the log that I consider pertinent to the issue at hand:
DEBUGWARNING - watchdog.watcher (10:17:12):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 190, in
File "core.pyo", line 384, in main
File "wx_core.pyo", line 8657, in MainLoop
File "wx_core.pyo", line 7952, in MainLoop
File "core.pyo", line 355, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "scriptHandler.pyo", line 144, in queueScriptCallback
File "scriptHandler.pyo", line 186, in executeScript
File "globalCommands.pyo", line 1398, in script_navigatorObject_devInfo
File "logging__init.pyo", line 1167, in info
File "logHandler.pyo", line 122, in _log
File "gui\logViewer.pyo", line 100, in activate
File "gui\logViewer.pyo", line 45, in init
File "gui\logViewer.pyo", line 54, in refresh
File "wx_core.pyo", line 13101, in AppendText
WARNING - watchdog.watcher (10:17:28):
Core frozen in stack:
File "nvda.pyw", line 190, in
File "core.pyo", line 384, in main
File "wx_core.pyo", line 8657, in MainLoop
File "wx_core.pyo", line 7952, in MainLoop
File "core.pyo", line 355, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "scriptHandler.pyo", line 144, in queueScriptCallback
File "scriptHandler.pyo", line 186, in executeScript
File "globalCommands.pyo", line 1398, in script_navigatorObject_devInfo
File "logging__init.pyo", line 1167, in info
File "logHandler.pyo", line 126, in _log
File "wx_core.pyo", line 13263, in SetInsertionPointEnd
Steps to reproduce
Open a a fairly large Microsoft Word document.
Switch to browse mode by pressing NVDA+Space.
Try a slightly intensive document reading command such as initiating a say all.
Now, immediately press NVDA+F1 to open the Log Viewer.
Expected Result: The Log Viewer should open without any hitch and NVDA should report it.
Actual Result: There is a significant freeze during this time, and NVDA takes a while to respond and announce the opening of the Log Viewer and begin reading its contents despite having issued necessary reading commands already.
Test Environment
Microsoft Office Word 2010
NVDA version 2016.3
Document of 84 pages (more or less pages should be able to demonstrate this problem consistently as well)
In my observation, NVDA functions very slowly and unresponsively in Microsoft Word's browse mode. Since I usually deal with school textbooks which span up to a few hundreds of pages, and sometimes toggle browse mode to use NVDA's additional functionalities in that state, I have constantly marked this delay. It It is my belief that the freeze that I am describing relates more to a flawed or problematic Word browse mode implementation as opposed to deficiencies in the Log Viewer.
In any case, here is a snippet of the log that I consider pertinent to the issue at hand:
DEBUGWARNING - watchdog.watcher (10:17:12):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 190, in
File "core.pyo", line 384, in main
File "wx_core.pyo", line 8657, in MainLoop
File "wx_core.pyo", line 7952, in MainLoop
File "core.pyo", line 355, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "scriptHandler.pyo", line 144, in queueScriptCallback
File "scriptHandler.pyo", line 186, in executeScript
File "globalCommands.pyo", line 1398, in script_navigatorObject_devInfo
File "logging__init.pyo", line 1167, in info
File "logHandler.pyo", line 122, in _log
File "gui\logViewer.pyo", line 100, in activate
File "gui\logViewer.pyo", line 45, in init
File "gui\logViewer.pyo", line 54, in refresh
File "wx_core.pyo", line 13101, in AppendText
WARNING - watchdog.watcher (10:17:28):
Core frozen in stack:
File "nvda.pyw", line 190, in
File "core.pyo", line 384, in main
File "wx_core.pyo", line 8657, in MainLoop
File "wx_core.pyo", line 7952, in MainLoop
File "core.pyo", line 355, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "scriptHandler.pyo", line 144, in queueScriptCallback
File "scriptHandler.pyo", line 186, in executeScript
File "globalCommands.pyo", line 1398, in script_navigatorObject_devInfo
File "logging__init.pyo", line 1167, in info
File "logHandler.pyo", line 126, in _log
File "wx_core.pyo", line 13263, in SetInsertionPointEnd