First off, I don’t know why crashing in the above subject got changed to “chasing” but in any case, I was able to get a debug log but it tells little more to me.
Essentially when control-two is typed which should switch the main Outlook view from what it is to the Calendar view, both NVDA and Outlook become unresponsive. It looks like NVDA pretty much just dies at
the control-2 if I am reading the below portion of the log correctly.
…
IO - speech.speak (15:14:29.400):
Speaking [LangChangeCommand ('en_GB'), u'unread From Iv\xe1n Novegil via Groups.Io, Subject Re: [nvda] Windows10 Mail and NVDA: several bugs reported, Received Mon 3/12/2018
2:21 PM, Size 86 KB,']
IO - inputCore.InputManager.executeGesture (15:14:35.358):
Input: kb(desktop):control+2
DEBUGWARNING - watchdog._watcher (15:14:37.355):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 212, in <module>
File "core.pyo", line 473, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 443, in Notify
File "IAccessibleHandler.pyo", line 894, in pumpAll
File "IAccessibleHandler.pyo", line 617, in processGenericWinEvent
File "IAccessibleHandler.pyo", line 521, in winEventToNVDAEvent
File "_UIAHandler.pyo", line 327, in isUIAWindow
File "_UIAHandler.pyo", line 315, in _isUIAWindowHelper
WARNING - watchdog._watcher (15:14:52.367):
Core frozen in stack:
File "nvda.pyw", line 212, in <module>
…
From: <nvda@nvda.groups.io> on behalf of "Cohn, Jonathan" <jcohn@...>
Reply-To: "nvda@nvda.groups.io" <nvda@nvda.groups.io>
Date: Friday, March 9, 2018 at 5:25 PM
To: "nvda@nvda.groups.io" <nvda@nvda.groups.io>
Subject: [nvda] NVDA chasing Outlook 365
Hello,
I have recreated this situation but not done any debugging.
NVDA 2018.1
Outlook 365
Windows 7 enterprise
- Open Outlook.
- Open a message and read it with numpad-+
Switch back to Inbox listing with alt-tab
Switch to calendar tab with control-2
At this point Outlook stops responding. I won’t be able to look at this further today, but besides simplifying down to not opening a message, what other actions
do I need to do before submitting a ticket?
How do I turn on debug log as I know that will be useful. Are additional details about versions required?
Thanks,
Jonathan Cohn
American Institutes for Research – Assessments
Web Accessibility specialist
