Re: continuing research into Outlook 2016 crashes on Windows 7


Jonathan COHN
 

Joseph,

 

Thanks, pretty much confirms my guesses though I still have a long way to go before understanding all the components of NVDA. In any case, the control-1, control-2, and control-3 commands in current versions of Outlook at least cause Outlook to crash when NVDA is running, but not when JAWS is running. As you specified this seems to be an ongoing issue and was reported with XP and Outlook 2007 so has been going on for a while if not this specific case. I suppose I could install 365 on my testing Windows 10  VM and see if this is a issue directly related to bad UIA within Win7. I just hate to leave a bug alone when I have source code and can accurately reproduce at will.

 

Though right now I need to verify that our implementation of Keylock is fully WCAG compliant. So, I might have to stick this away for a weekend project.

 

Thanks,

 

Jonathan

 

From: <nvda@nvda.groups.io> on behalf of Joseph Lee <joseph.lee22590@...>
Reply-To: "nvda@nvda.groups.io" <nvda@nvda.groups.io>
Date: Tuesday, March 13, 2018 at 4:24 PM
To: "nvda@nvda.groups.io" <nvda@nvda.groups.io>
Subject: Re: [nvda] continuing research into Outlook 2016 crashes on Windows 7

 

Hi,

I see. In short, from what I can tell, UIA bridge freezes when trying to obtain something from an app. There are numerous itHub issues regarding this problem.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Cohn, Jonathan
Sent: Tuesday, March 13, 2018 1:16 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] continuing research into Outlook 2016 crashes on Windows 7

 

OK, not quite sure but since my first query did not provide any information I decided to plow ahead.

 

Basic information from logs are:

  1. -2 typed.

Next item in NVDA log is: DEBUGWARNING - watchdog._watcher (15:14:37.355):

 

Followed by a couple of

WARNING - watchdog._watcher (15:14:52.367): Core frozen in stack:

 

WARNING - watchdog._watcher (15:15:07.414):

Core frozen in stack

 

 

At which point NVDA stops talking. After getting speech back through another screen reder, Outlook has a not responding message.

 

When I did a switch from Calendar View to Messages view I also got a debug watch dog but NVDA seemed to be able to clear it out with the following:

IO - inputCore.InputManager.executeGesture (15:14:12.845):

Input: kb(desktop):control+1

DEBUGWARNING - watchdog._watcher (15:14:14.868):

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

 

DEBUGWARNING - core.CorePump.Notify (15:14:15.085):

errors in this core pump cycle

Traceback (most recent call last):

  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 321, in _isUIAWindowHelper

  File "watchdog.pyo", line 195, in sendMessageCallCanceller

CallCancelled

IO - inputCore.InputManager.executeGesture (15:14:15.493):

Input: kb(desktop):NVDA+t

DEBUGWARNING - watchdog._watcher (15:14:15.592):

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 880, in pumpAll

  File "IAccessibleHandler.pyo", line 654, in processFocusWinEvent

  File "IAccessibleHandler.pyo", line 521, in winEventToNVDAEvent

  File "_UIAHandler.pyo", line 327, in isUIAWindow

  File "_UIAHandler.pyo", line 315, in _isUIAWindowHelper

 

DEBUGWARNING - core.CorePump.Notify (15:14:15.911):

errors in this core pump cycle

Traceback (most recent call last):

  File "core.pyo", line 443, in Notify

  File "IAccessibleHandler.pyo", line 880, in pumpAll

  File "IAccessibleHandler.pyo", line 654, in processFocusWinEvent

  File "IAccessibleHandler.pyo", line 521, in winEventToNVDAEvent

  File "_UIAHandler.pyo", line 327, in isUIAWindow

  File "_UIAHandler.pyo", line 321, in _isUIAWindowHelper

  File "watchdog.pyo", line 195, in sendMessageCallCanceller

CallCancelled

DEBUGWARNING - watchdog._watcher (15:14:16.437):

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 880, in pumpAll

  File "IAccessibleHandler.pyo", line 654, in processFocusWinEvent

  File "IAccessibleHandler.pyo", line 521, in winEventToNVDAEvent

  File "_UIAHandler.pyo", line 327, in isUIAWindow

  File "_UIAHandler.pyo", line 315, in _isUIAWindowHelper

 

DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.974):

oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728967 and childID 0: [Error -2147467259] Unspecified error

DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976):

oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728905 and childID 0: [Error -2147467259] Unspecified error

DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976):

oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728906 and childID 0: [Error -2147467259] Unspecified error

DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976):

oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728901 and childID 0: [Error -2147467259] Unspecified error

DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976):

oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728907 and childID 0: [Error -2147467259] Unspecified error

DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976):

oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728908 and childID 0: [Error -2147467259] Unspecified error

DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976):

oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728909 and childID 0: [Error -2147467259] Unspecified error

DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976):

oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728910 and childID 0: [Error -2147467259] Unspecified error

DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.977):

oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728911 and childID 0: [Error -2147467259] Unspecified error

IO - speech.speak (15:14:19.016):

Speaking [LangChangeCommand ('en_GB'), u'Inbox - jcohn@... - Outlook']

 

 

 

Trying to recover from freeze, core stack

 

 

From: <nvda@nvda.groups.io> on behalf of Joseph Lee <joseph.lee22590@...>
Reply-To: "nvda@nvda.groups.io" <nvda@nvda.groups.io>
Date: Tuesday, March 13, 2018 at 3:41 PM
To: "nvda@nvda.groups.io" <nvda@nvda.groups.io>
Subject: Re: [nvda] continuing research into Outlook 2016 crashes on Windows 7

 

Hi,

In order to verify your claim, I need an evidence please.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Cohn, Jonathan
Sent: Tuesday, March 13, 2018 12:12 PM
To:
nvda@nvda.groups.io
Subject: [nvda] continuing research into Outlook 2016 crashes on Windows 7

 

OK, some research makes me think that when I use the keyboard shortcut to change from Mailbox view to Calendar View in Outlook that the crash might be related to UIA not being handled correctly. Is there a way I could disable UIA for my copy of NVDA either in intirety or for Outlook just to execute this command without working with the NVDA core? I

 

So, could I write a Outlook addon that disables UIA when in the SuperGrid or in the INI files?

 

Thanks!

 

Jonathan Cohn

 

 

Join {nvda@nvda.groups.io to automatically receive all group messages.