Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors sometimes occur when closing IE8 with other apps or folders open #3804

Closed
nvaccessAuto opened this issue Jan 22, 2014 · 6 comments
Closed

Comments

@nvaccessAuto
Copy link

Reported by briang1 on 2014-01-22 19:29

I had Outlook Express open and IE open and had gone to a page from a link in an email. Once i'd finished on that page, i closed Internet Explorer with alt/f4.

IO - speech.speak (12:13:41):
Speaking ('en_GB'), u'Health and Wellbeing Board -
Download audio recordings of committee meetings - The Royal Boroug - Windows
Internet Explorer'

IO - inputCore.InputManager.executeGesture (12:13:41):
Input: kb(desktop):alt+f4
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (12:13:41):
oleacc.AccessibleObjectFromEvent with window 1311708, objectID -4 and
childID 0: -2147024809 The parameter is incorrect
DEBUG - treeInterceptorHandler.killTreeInterceptor (12:13:41):
Killed treeInterceptor: <virtualBuffers.MSHTML.MSHTML object at 0x03C5F650>
DEBUGWARNING - eventHandler.executeEvent (12:13:41):
error executing event: gainFocus on
<NVDAObjects.Dynamic_EditableTextWithoutAutoSelectDetectionBodyMSHTMLIAccessibleWindowNVDAObject
object at 0x03D5AE10> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 131, in executeEvent
File "eventHandler.pyc", line 144, in doPreGainFocus
File "api.pyc", line 122, in setFocusObject
File "treeInterceptorHandler.pyc", line 34, in update
File "virtualBuffers\MSHTML.pyc", line 143, in init
File "virtualBuffers__init__.pyc", line 581, in init
File "virtualBuffers\MSHTML.pyc", line 221, in getIdentifierFromNVDAObject
File "baseObject.pyc", line 34, in get
File "baseObject.pyc", line 110, in getPropertyViaCache
File "NVDAObjects\IAccessible\MSHTML.pyc", line 822, in
get_HTMLNodeUniqueNumber
File "comtypesMonkeyPatches.pyc", line 32, in new__getattr

File "comtypes\client\lazybind.pyc", line 149, in getattr
File "comtypes\automation.pyc", line 664, in _invoke
COMError: (-2147024891, 'Access is denied.', (None, None, None, 0, None))
ERROR - eventHandler.executeEvent (12:13:41):
error executing event: gainFocus on <NVDAObjects.IAccessible.MSHTML.MSHTML
object at 0x03D69B10> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 131, in executeEvent
File "eventHandler.pyc", line 144, in doPreGainFocus
File "api.pyc", line 113, in setFocusObject
File "appModuleHandler.pyc", line 222, in handleAppSwitch
AttributeError: 'NoneType' object has no attribute 'exit'
ERROR - eventHandler.executeEvent (12:13:41):
error executing event: gainFocus on <NVDAObjects.IAccessible.IAccessible
object at 0x01EFAEB0> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 131, in executeEvent
File "eventHandler.pyc", line 144, in doPreGainFocus
File "api.pyc", line 113, in setFocusObject
File "appModuleHandler.pyc", line 222, in handleAppSwitch
AttributeError: 'NoneType' object has no attribute 'exit'
ERROR - eventHandler.executeEvent (12:13:41):
error executing event: gainFocus on
<NVDAObjects.IAccessible.sysListView32.ListItem object at 0x03D5A6F0> with
extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 131, in executeEvent
File "eventHandler.pyc", line 144, in doPreGainFocus
File "api.pyc", line 113, in setFocusObject
File "appModuleHandler.pyc", line 222, in handleAppSwitch
AttributeError: 'NoneType' object has no attribute 'exit'
IO - inputCore.InputManager.executeGesture (12:13:49):
Input: kb(desktop):control+alt+r
INFO - core.main (12:13:51):
Exiting

It seems to happen that this error occurs intermittently. Its probably speed related on when nvda looks at the data from the current window. On XP older machines this can be longer so one assumes there is more opportunity to get some misleading data!

Note that I felt sure this had a ticket already, but could not locate it.
Blocking #3847

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2014-01-22 23:03
I thought this had a ticket too, but I can't find it either. :)

Anyway, I think I missed something important in the log the first time you posted this. I now have a clue as to what is causing this, so I can hopefully fix it. Thanks for filing.

@nvaccessAuto
Copy link
Author

Comment 2 by briang1 on 2014-01-25 13:59
I've not seen this for a couple of days now, but there have been odd errors that also mention the task switching etc, they seem to be totally random. Most seem to do no lasting harm that I can detect. Maybe they should be just set to warnings?

@nvaccessAuto
Copy link
Author

Comment 3 by James Teh <jamie@... on 2014-01-27 01:01
In [8f405f3]:

Fix issues with application profile triggers when creating a virtual buffer fails.

If creating a virtual buffer failed in api.setFocusObject, the global focus variables weren't set, but application triggers were already exited/entered. This meant that next time the focus changed, NVDA tried to exit triggers that had already been exited. Also, there may have been triggers entered that were never exited.
Exceptions from treeInterceptorHandler.update are now caught. Also, the call to handleAppSwitch has been moved as late as possible so other exceptions don't cause this problem. Ideally, there aren't any other possible exceptions like this, but it's best to be safe.
Re #3804.

@nvaccessAuto
Copy link
Author

Comment 4 by James Teh <jamie@... on 2014-01-27 01:02
In [4e82e65]:

Merge branch 't3804' into next

Incubates #3804.

Changes:
Added labels: incubating

@nvaccessAuto
Copy link
Author

Comment 6 by James Teh <jamie@... on 2014-02-11 03:28
In [f296818]:

Fix issues with application profile triggers when creating a virtual buffer fails.

If creating a virtual buffer failed in api.setFocusObject, the global focus variables weren't set, but application triggers were already exited/entered. This meant that next time the focus changed, NVDA tried to exit triggers that had already been exited. Also, there may have been triggers entered that were never exited.
Exceptions from treeInterceptorHandler.update are now caught. Also, the call to handleAppSwitch has been moved as late as possible so other exceptions don't cause this problem. Ideally, there aren't any other possible exceptions like this, but it's best to be safe.
Fixes #3804.

Changes:
Removed labels: incubating
State: closed

@nvaccessAuto
Copy link
Author

Comment 7 by jteh on 2014-02-11 03:32
Changes:
Milestone changed from None to 2014.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants