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

Firefox does not gain focus when started from Windows 7 with latest snapshots #4296

Closed
nvaccessAuto opened this issue Jul 15, 2014 · 21 comments

Comments

@nvaccessAuto
Copy link

Reported by briang1 on 2014-07-15 21:51
Firstly, I see another ticket with similar problems, but to me at least this is different enough to need a new ticket.
How to get the effect.
Boot up xp and launch firefox 31 from the desktop shortcut.
Most of the times Firefox never puts in any apparence. However it is there, as can be found by just pressing alt, or space or a cursor key.
Nvda seems to think its still on the desktop.
I am going to attach a log I generated with comments earlier.
Note that this effect is not in 2014.2, only in master and next snaps for some versions now.
Sometimes it will work, but not all that often. There appears to be some kind of looping going on somewhere.

@nvaccessAuto
Copy link
Author

nvaccessAuto commented Jul 15, 2014

Attachment firefox no focus.log added by briang1 on 2014-07-15 21:53
Description:
log of two launches of firefox that do not get focus without help
Update:
File attached from Trac
firefox no focus.log.txt

@nvaccessAuto
Copy link
Author

Comment 1 by briang1 on 2014-07-15 22:46
I have confirmed that the issue goes away if watchdog is disabled with
import watchdog; watchdog.terminate()

There seems to be no ill effects from doing this.

@nvaccessAuto
Copy link
Author

Comment 2 by jteh on 2014-07-16 01:05
I really don't wish to contradict you--I'm sure you've done everything you can to verify this--but I need to be absolutely certain: does this definitely happen on master snapshots? I might be able to understand it happening on next, but I can't think of any recent change on master that should cause something like this.

@nvaccessAuto
Copy link
Author

Comment 3 by briang1 on 2014-07-16 07:12
Well, on further research, i think the problem in Master is slightly different both in its likelyhood and the errors generated.
it seems for some odd reason focus jumps back to desktop part way through the load and it is actually looking at mshtml. Also the single key to get focus back does not work, unless its the alt key to bring up a menu.
I'll attach a log of Master, a portable version.

@nvaccessAuto
Copy link
Author

nvaccessAuto commented Jul 16, 2014

Attachment firefox no focus master.log added by briang1 on 2014-07-16 07:15
Description:
A log from the latest master snapshot of first load of firefox 31
Update:
File attached from Trac
firefox no focus master.log.txt

@nvaccessAuto
Copy link
Author

Comment 4 by briang1 on 2014-07-17 22:36
My latest tests seem to show that this happens due toFirefox using a lot of processor time, and it seems that some changes in nvda have affected nvdas ability to still function in this condition.
I have I think proved this with a small batch file to run Firefox with belo normal processor usage.
Something like.
@echo off
cls
start /belownormal firefox.exe
exit
Which seems to cure the start up problem in both snapshots.

IO - speech.speak (23:13:56):
Speaking ('en_GB'), u'Mozilla Firefox 8 of 41'
DEBUG - queueHandler.pumpAll (23:13:56):
generator 89 finished
IO - inputCore.InputManager.executeGesture (23:13:58):
Input: kb(desktop):enter
DEBUGWARNING - watchdog.watcher (23:14:05):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 181, in
File "core.pyc", line 346, in main
File "wx_core.pyc", line 8010, in MainLoop
File "wx_core.pyc", line 7306, in MainLoop
File "core.pyc", line 316, in Notify
File "IAccessibleHandler.pyc", line 861, in pumpAll
File "IAccessibleHandler.pyc", line 747, in processForegroundWinEvent
File "IAccessibleHandler.pyc", line 524, in winEventToNVDAEvent
File "NVDAObjects\IAccessible__init
_.pyc", line 37, in getNVDAObjectFromEvent
File "IAccessibleHandler.pyc", line 339, in accessibleObjectFromEvent
File "oleacc.pyc", line 240, in AccessibleObjectFromEvent

IO - speech.speak (23:14:05):
Speaking ('en_GB'), u'Mozilla Firefox'
DEBUGWARNING - NVDAObjects.IAccessible.Dynamic_DocumentBrokenFocusedStateMozillaIAccessible._get_IA2Attributes (23:14:07):
IAccessibleObject.attributes COMError (-2147220995, 'Object is not connected to server', (None, None, None, 0, None))
IO - speech.speak (23:14:07):
Speaking ('en_GB'), u'Startpage Web Search - Mozilla Firefox'
IO - speech.speak (23:14:07):
Speaking ('en_GB'), u'unknown'
DEBUG - treeInterceptorHandler.update (23:14:08):
Adding new treeInterceptor to runningTable: <virtualBuffers.gecko_ia2.Gecko_ia2 object at 0x04064C90>
IO - speech.speak (23:14:08):
Speaking ('en_GB'), u'Startpage Web Search - Mozilla Firefox'
IO - speech.speak (23:14:08):
Speaking ('en_GB'), u'Startpage Web Search document'
IO - speech.speak (23:14:08):
Speaking ('en_GB'), u'Startpage Web Search - Mozilla Firefox'
IO - speech.speak (23:14:08):
Speaking ('en_GB'), u'Startpage Web Search document'
IO - speech.speak (23:14:08):
Speaking ('en_GB'), u'edit'
IO - speech.speak (23:14:08):
Speaking ('en_GB'), u'blank'
IO - speech.speak (23:14:08):
Speaking ('en_GB'), u'focus mode'

So far this does not seem to cause Firefox a problem, but I've probably not tested it enough.
This is a single core issue perhaps?

@nvaccessAuto
Copy link
Author

Comment 5 by msuch (in reply to comment description) on 2015-01-22 08:32
Replying to briang1:
This problem occurs more and more often. I run W7 on several machines with Firefox 35. It used to happen only on slow machines (a netbook running W7 starter), but now it also occurs on a big desktop machine. Once Ff is started, you need to play with alt+tab so that NVDA finally sees that Ff gained focus.

Firstly, I see another ticket with similar problems, but to me at least this is different enough to need a new ticket.

How to get the effect.

Boot up xp and launch firefox 31 from the desktop shortcut.

Most of the times Firefox never puts in any apparence. However it is there, as can be found by just pressing alt, or space or a cursor key.

Nvda seems to think its still on the desktop.

I am going to attach a log I generated with comments earlier.

Note that this effect is not in 2014.2, only in master and next snaps for some versions now.

Sometimes it will work, but not all that often. There appears to be some kind of looping going on somewhere.

@nvaccessAuto
Copy link
Author

Comment 6 by jteh (in reply to comment 5) on 2015-01-22 21:31
Replying to msuch:

This problem occurs more and more often.

For you, does it occur only in next or also in master/release? I can understand it occurring in next, but not the others.

@nvaccessAuto
Copy link
Author

Comment 7 by msuch (in reply to comment 6) on 2015-01-22 21:57
Replying to jteh:

Replying to msuch:

This problem occurs more and more often.

For you, does it occur only in next or also in master/release? I can understand it occurring in next, but not the others.

Yes, with latest next versions, it occurs on all my machines. With all previous version for a long time, it only uccured on my slow netbook.

@nvaccessAuto
Copy link
Author

Comment 8 by msuch (in reply to comment 7) on 2015-01-23 09:42
Waw, it works just fine with latest Next 11520,522dc25.
It works fine even on my slowest machine where it was broken for months.
You can notice the improvement even during the update where the update progress windows comes more easily to foreground.
Bravo !
Replying to msuch:

Replying to jteh:

Replying to msuch:

This problem occurs more and more often.

For you, does it occur only in next or also in master/release? I can understand it occurring in next, but not the others.

Yes, with latest next versions, it occurs on all my machines. With all previous version for a long time, it only uccured on my slow netbook.

@nvaccessAuto
Copy link
Author

Comment 9 by briang1 on 2015-01-23 11:10
Pardon me for this little spanner in the works, but I'm seeing no real improvement for Firefox launch in XP. I've not tried Windows 7 yet. However as mentioned, Master etc, seems a whole lot better in this respect.
Here is the log of starting firefox 36 with the latest next in xp on my fastest single core machine.

INFO - main (10:54:02):
Starting NVDA
INFO - core.main (10:54:02):
Config dir: C:\Documents and Settings\brian\Application Data\nvda
DEBUG - core.main (10:54:02):
setting language to Windows
INFO - core.main (10:54:02):
NVDA version next-11520,522dc25
INFO - core.main (10:54:02):
Using Windows version sys.getwindowsversion(major=5, minor=1, build=2600, platform=2, service_pack='Service Pack 3')
INFO - core.main (10:54:02):
Using Python version 2.7.9 (default, Dec 10 2014, 12:24:55) v.1500 32 bit (Intel)
INFO - core.main (10:54:02):
Using comtypes version 0.6.2
=== snip of start up routine.
DEBUG - core.main (10:54:03):
entering wx application main loop
IO - speech.speak (10:54:03):
Speaking ('en_GB'), u'Desktop list'
IO - speech.speak (10:54:03):
Speaking ('en_GB'), u'Mozilla Firefox 13 of 66'
IO - inputCore.InputManager.executeGesture (10:54:08):
Input: kb(desktop):upArrow
IO - speech.speak (10:54:08):
Speaking ('en_GB'), u'Jarte 12 of 66'
IO - inputCore.InputManager.executeGesture (10:54:09):
Input: kb(desktop):downArrow
IO - speech.speak (10:54:09):
Speaking ('en_GB'), u'Mozilla Firefox 13 of 66'
IO - speech.speak (10:54:10):
Speaking ('en_GB'), u'Location: C:\Program Files\Mozilla Firefox tool tip'
IO - inputCore.InputManager.executeGesture (10:54:13):
Input: kb(desktop):enter
DEBUGWARNING - watchdog.watcher (10:54:15):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 184, in
File "core.pyc", line 370, in main
File "wx_core.pyc", line 8657, in MainLoop
File "wx_core.pyc", line 7952, in MainLoop
File "core.pyc", line 340, in Notify
File "IAccessibleHandler.pyc", line 858, in pumpAll
File "IAccessibleHandler.pyc", line 742, in processForegroundWinEvent
File "IAccessibleHandler.pyc", line 523, in winEventToNVDAEvent
File "NVDAObjects\IAccessible__init
_.pyc", line 37, in getNVDAObjectFromEvent
File "IAccessibleHandler.pyc", line 338, in accessibleObjectFromEvent
File "oleacc.pyc", line 240, in AccessibleObjectFromEvent

DEBUGWARNING - core.Notify (10:54:16):
errors in this core pump cycle
Traceback (most recent call last):
File "core.pyc", line 340, in Notify
File "IAccessibleHandler.pyc", line 858, in pumpAll
File "IAccessibleHandler.pyc", line 742, in processForegroundWinEvent
File "IAccessibleHandler.pyc", line 523, in winEventToNVDAEvent
File "NVDAObjects\IAccessible__init__.pyc", line 43, in getNVDAObjectFromEvent
File "NVDAObjects__init__.pyc", line 68, in call
File "watchdog.pyc", line 192, in COMError_init
CallCancelled
DEBUGWARNING - watchdog.watcher (10:54:16):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 184, in
File "core.pyc", line 370, in main
File "wx_core.pyc", line 8657, in MainLoop
File "wx_core.pyc", line 7952, in MainLoop
File "core.pyc", line 340, in Notify
File "IAccessibleHandler.pyc", line 843, in pumpAll
File "IAccessibleHandler.pyc", line 642, in processFocusWinEvent
File "IAccessibleHandler.pyc", line 523, in winEventToNVDAEvent
File "NVDAObjects\IAccessible__init
.pyc", line 43, in getNVDAObjectFromEvent
File "NVDAObjects__init__.pyc", line 68, in call
File "NVDAObjects\IAccessible__init__.pyc", line 599, in init
File "comtypes__init__.pyc", line 1078, in QueryInterface

DEBUGWARNING - core.Notify (10:54:17):
errors in this core pump cycle
Traceback (most recent call last):
File "core.pyc", line 340, in Notify
File "IAccessibleHandler.pyc", line 843, in pumpAll
File "IAccessibleHandler.pyc", line 642, in processFocusWinEvent
File "IAccessibleHandler.pyc", line 523, in winEventToNVDAEvent
File "NVDAObjects\IAccessible__init__.pyc", line 43, in getNVDAObjectFromEvent
File "NVDAObjects__init__.pyc", line 68, in call
File "watchdog.pyc", line 192, in COMError_init
CallCancelled
DEBUGWARNING - watchdog.watcher (10:54:17):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 184, in
File "core.pyc", line 370, in main
File "wx_core.pyc", line 8657, in MainLoop
File "wx_core.pyc", line 7952, in MainLoop
File "core.pyc", line 340, in Notify
File "IAccessibleHandler.pyc", line 855, in pumpAll
File "IAccessibleHandler.pyc", line 605, in processGenericWinEvent
File "IAccessibleHandler.pyc", line 523, in winEventToNVDAEvent
File "NVDAObjects\IAccessible__init
.pyc", line 43, in getNVDAObjectFromEvent
File "NVDAObjects__init__.pyc", line 68, in call
File "NVDAObjects\IAccessible__init__.pyc", line 537, in init

DEBUGWARNING - core.Notify (10:54:18):
errors in this core pump cycle
Traceback (most recent call last):
File "core.pyc", line 340, in Notify
File "IAccessibleHandler.pyc", line 855, in pumpAll
File "IAccessibleHandler.pyc", line 605, in processGenericWinEvent
File "IAccessibleHandler.pyc", line 523, in winEventToNVDAEvent
File "NVDAObjects\IAccessible__init__.pyc", line 43, in getNVDAObjectFromEvent
File "NVDAObjects__init__.pyc", line 68, in call
File "watchdog.pyc", line 192, in COMError_init
CallCancelled
DEBUGWARNING - watchdog.watcher (10:54:18):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 184, in
File "core.pyc", line 370, in main
File "wx_core.pyc", line 8657, in MainLoop
File "wx_core.pyc", line 7952, in MainLoop
File "core.pyc", line 340, in Notify
File "IAccessibleHandler.pyc", line 855, in pumpAll
File "IAccessibleHandler.pyc", line 605, in processGenericWinEvent
File "IAccessibleHandler.pyc", line 523, in winEventToNVDAEvent
File "NVDAObjects\IAccessible__init
.pyc", line 37, in getNVDAObjectFromEvent
File "IAccessibleHandler.pyc", line 338, in accessibleObjectFromEvent
File "oleacc.pyc", line 240, in AccessibleObjectFromEvent

DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (10:54:19):
oleacc.AccessibleObjectFromEvent with window 459340, objectID -4 and childID -244401776:
DEBUGWARNING - watchdog.watcher (10:54:21):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 184, in
File "core.pyc", line 370, in main
File "wx_core.pyc", line 8657, in MainLoop
File "wx_core.pyc", line 7952, in MainLoop
File "core.pyc", line 340, in Notify
File "IAccessibleHandler.pyc", line 855, in pumpAll
File "IAccessibleHandler.pyc", line 605, in processGenericWinEvent
File "IAccessibleHandler.pyc", line 523, in winEventToNVDAEvent
File "NVDAObjects\IAccessible__init
_.pyc", line 43, in getNVDAObjectFromEvent
File "NVDAObjects__init__.pyc", line 58, in call
File "NVDAObjects__init__.pyc", line 187, in findBestAPIClass
File "NVDAObjects\IAccessible\MSHTML.pyc", line 425, in kwargsFromSuper
File "NVDAObjects\IAccessible\MSHTML.pyc", line 150, in HTMLNodeFromIAccessible
File "comtypes__init__.pyc", line 1111, in QueryService

IO - speech.speak (10:54:44):
Speaking ('en_GB'), u'Startpage Search Engine - Mozilla Firefox'
IO - speech.speak (10:54:44):
Speaking ('en_GB'), u'Menu Bar tool bar'
IO - speech.speak (10:54:44):
Speaking ('en_GB'), u'File subMenu Alt+F 1 of 7'
IO - inputCore.InputManager.executeGesture (10:54:45):
Input: kb(desktop):escape
DEBUG - treeInterceptorHandler.update (10:54:45):
Adding new treeInterceptor to runningTable: <virtualBuffers.gecko_ia2.Gecko_ia2 object at 0x0317F8F0>
IO - speech.speak (10:54:46):
Speaking ('en_GB'), u'Startpage Search Engine document'
IO - speech.speak (10:54:46):
Speaking ('en_GB'), u'Startpage Search Engine document'
IO - speech.speak (10:54:46):
Speaking ('en_GB'), u'edit'
IO - speech.speak (10:54:46):
Speaking ('en_GB'), u'blank'
IO - speech.speak (10:54:46):
Speaking ('en_GB'), u'focus mode'

I don't quite see what is happening but it looks like it never detects the fact that it needs to create a buffer until I press a key and make Firefox magically appear to nvda, which otherwise is confused.

@nvaccessAuto
Copy link
Author

Comment 10 by msuch (in reply to comment 9) on 2015-01-23 13:39
Well, you are right, I was a little to much anthousiastic.
It is better but still not perfect.
On my slow machine it sometimes work and sometimes not.
Beside this problem, there is another one which maybe is the same.
When you close an application, the system brings to foreground the last window you were on before using the app.
So NVDA gets to it, but you can't act on it until you leave it and return to it.
This is a very old problem, probably difficult to fix.

Replying to briang1:

Pardon me for this little spanner in the works, but I'm seeing no real improvement for Firefox launch in XP. I've not tried Windows 7 yet. However as mentioned, Master etc, seems a whole lot better in this respect.

Here is the log of starting firefox 36 with the latest next in xp on my fastest single core machine.

INFO - main (10:54:02):

Starting NVDA

INFO - core.main (10:54:02):

Config dir: C:\Documents and Settings\brian\Application Data\nvda

DEBUG - core.main (10:54:02):

setting language to Windows

INFO - core.main (10:54:02):

NVDA version next-11520,522dc25

INFO - core.main (10:54:02):

Using Windows version sys.getwindowsversion(major=5, minor=1, build=2600, platform=2, service_pack='Service Pack 3')

INFO - core.main (10:54:02):

Using Python version 2.7.9 (default, Dec 10 2014, 12:24:55) v.1500 32 bit (Intel)

INFO - core.main (10:54:02):

Using comtypes version 0.6.2

=== snip of start up routine.

DEBUG - core.main (10:54:03):

entering wx application main loop

IO - speech.speak (10:54:03):

Speaking ('en_GB'), u'Desktop list'

IO - speech.speak (10:54:03):

Speaking ('en_GB'), u'Mozilla Firefox 13 of 66'

IO - inputCore.InputManager.executeGesture (10:54:08):

Input: kb(desktop):upArrow

IO - speech.speak (10:54:08):

Speaking ('en_GB'), u'Jarte 12 of 66'

IO - inputCore.InputManager.executeGesture (10:54:09):

Input: kb(desktop):downArrow

IO - speech.speak (10:54:09):

Speaking ('en_GB'), u'Mozilla Firefox 13 of 66'

IO - speech.speak (10:54:10):

Speaking ('en_GB'), u'Location: C:\Program Files\Mozilla Firefox tool tip'

IO - inputCore.InputManager.executeGesture (10:54:13):

Input: kb(desktop):enter

DEBUGWARNING - watchdog._watcher (10:54:15):

Trying to recover from freeze, core stack:

File "nvda.pyw", line 184, in

File "core.pyc", line 370, in main

File "wx_core.pyc", line 8657, in MainLoop

File "wx_core.pyc", line 7952, in MainLoop

File "core.pyc", line 340, in Notify

File "IAccessibleHandler.pyc", line 858, in pumpAll

File "IAccessibleHandler.pyc", line 742, in processForegroundWinEvent

File "IAccessibleHandler.pyc", line 523, in winEventToNVDAEvent

File "NVDAObjects\IAccessible__init__.pyc", line 37, in getNVDAObjectFromEvent

File "IAccessibleHandler.pyc", line 338, in accessibleObjectFromEvent

File "oleacc.pyc", line 240, in AccessibleObjectFromEvent

DEBUGWARNING - core.Notify (10:54:16):

errors in this core pump cycle

Traceback (most recent call last):

File "core.pyc", line 340, in Notify

File "IAccessibleHandler.pyc", line 858, in pumpAll

File "IAccessibleHandler.pyc", line 742, in processForegroundWinEvent

File "IAccessibleHandler.pyc", line 523, in winEventToNVDAEvent

File "NVDAObjects\IAccessible__init__.pyc", line 43, in getNVDAObjectFromEvent

File "NVDAObjects__init__.pyc", line 68, in call

File "watchdog.pyc", line 192, in _COMError_init

CallCancelled

DEBUGWARNING - watchdog._watcher (10:54:16):

Trying to recover from freeze, core stack:

File "nvda.pyw", line 184, in

File "core.pyc", line 370, in main

File "wx_core.pyc", line 8657, in MainLoop

File "wx_core.pyc", line 7952, in MainLoop

File "core.pyc", line 340, in Notify

File "IAccessibleHandler.pyc", line 843, in pumpAll

File "IAccessibleHandler.pyc", line 642, in processFocusWinEvent

File "IAccessibleHandler.pyc", line 523, in winEventToNVDAEvent

File "NVDAObjects\IAccessible__init__.pyc", line 43, in getNVDAObjectFromEvent

File "NVDAObjects__init__.pyc", line 68, in call

File "NVDAObjects\IAccessible__init__.pyc", line 599, in init

File "comtypes__init__.pyc", line 1078, in QueryInterface

DEBUGWARNING - core.Notify (10:54:17):

errors in this core pump cycle

Traceback (most recent call last):

File "core.pyc", line 340, in Notify

File "IAccessibleHandler.pyc", line 843, in pumpAll

File "IAccessibleHandler.pyc", line 642, in processFocusWinEvent

File "IAccessibleHandler.pyc", line 523, in winEventToNVDAEvent

File "NVDAObjects\IAccessible__init__.pyc", line 43, in getNVDAObjectFromEvent

File "NVDAObjects__init__.pyc", line 68, in call

File "watchdog.pyc", line 192, in _COMError_init

CallCancelled

DEBUGWARNING - watchdog._watcher (10:54:17):

Trying to recover from freeze, core stack:

File "nvda.pyw", line 184, in

File "core.pyc", line 370, in main

File "wx_core.pyc", line 8657, in MainLoop

File "wx_core.pyc", line 7952, in MainLoop

File "core.pyc", line 340, in Notify

File "IAccessibleHandler.pyc", line 855, in pumpAll

File "IAccessibleHandler.pyc", line 605, in processGenericWinEvent

File "IAccessibleHandler.pyc", line 523, in winEventToNVDAEvent

File "NVDAObjects\IAccessible__init__.pyc", line 43, in getNVDAObjectFromEvent

File "NVDAObjects__init__.pyc", line 68, in call

File "NVDAObjects\IAccessible__init__.pyc", line 537, in init

DEBUGWARNING - core.Notify (10:54:18):

errors in this core pump cycle

Traceback (most recent call last):

File "core.pyc", line 340, in Notify

File "IAccessibleHandler.pyc", line 855, in pumpAll

File "IAccessibleHandler.pyc", line 605, in processGenericWinEvent

File "IAccessibleHandler.pyc", line 523, in winEventToNVDAEvent

File "NVDAObjects\IAccessible__init__.pyc", line 43, in getNVDAObjectFromEvent

File "NVDAObjects__init__.pyc", line 68, in call

File "watchdog.pyc", line 192, in _COMError_init

CallCancelled

DEBUGWARNING - watchdog._watcher (10:54:18):

Trying to recover from freeze, core stack:

File "nvda.pyw", line 184, in

File "core.pyc", line 370, in main

File "wx_core.pyc", line 8657, in MainLoop

File "wx_core.pyc", line 7952, in MainLoop

File "core.pyc", line 340, in Notify

File "IAccessibleHandler.pyc", line 855, in pumpAll

File "IAccessibleHandler.pyc", line 605, in processGenericWinEvent

File "IAccessibleHandler.pyc", line 523, in winEventToNVDAEvent

File "NVDAObjects\IAccessible__init__.pyc", line 37, in getNVDAObjectFromEvent

File "IAccessibleHandler.pyc", line 338, in accessibleObjectFromEvent

File "oleacc.pyc", line 240, in AccessibleObjectFromEvent

DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (10:54:19):

oleacc.AccessibleObjectFromEvent with window 459340, objectID -4 and childID -244401776:

DEBUGWARNING - watchdog._watcher (10:54:21):

Trying to recover from freeze, core stack:

File "nvda.pyw", line 184, in

File "core.pyc", line 370, in main

File "wx_core.pyc", line 8657, in MainLoop

File "wx_core.pyc", line 7952, in MainLoop

File "core.pyc", line 340, in Notify

File "IAccessibleHandler.pyc", line 855, in pumpAll

File "IAccessibleHandler.pyc", line 605, in processGenericWinEvent

File "IAccessibleHandler.pyc", line 523, in winEventToNVDAEvent

File "NVDAObjects\IAccessible__init__.pyc", line 43, in getNVDAObjectFromEvent

File "NVDAObjects__init__.pyc", line 58, in call

File "NVDAObjects__init__.pyc", line 187, in findBestAPIClass

File "NVDAObjects\IAccessible\MSHTML.pyc", line 425, in kwargsFromSuper

File "NVDAObjects\IAccessible\MSHTML.pyc", line 150, in HTMLNodeFromIAccessible

File "comtypes__init__.pyc", line 1111, in QueryService

IO - speech.speak (10:54:44):

Speaking ('en_GB'), u'Startpage Search Engine - Mozilla Firefox'

IO - speech.speak (10:54:44):

Speaking ('en_GB'), u'Menu Bar tool bar'

IO - speech.speak (10:54:44):

Speaking ('en_GB'), u'File subMenu Alt+F 1 of 7'

IO - inputCore.InputManager.executeGesture (10:54:45):

Input: kb(desktop):escape

DEBUG - treeInterceptorHandler.update (10:54:45):

Adding new treeInterceptor to runningTable: <virtualBuffers.gecko_ia2.Gecko_ia2 object at 0x0317F8F0>

IO - speech.speak (10:54:46):

Speaking ('en_GB'), u'Startpage Search Engine document'

IO - speech.speak (10:54:46):

Speaking ('en_GB'), u'Startpage Search Engine document'

IO - speech.speak (10:54:46):

Speaking ('en_GB'), u'edit'

IO - speech.speak (10:54:46):

Speaking ('en_GB'), u'blank'

IO - speech.speak (10:54:46):

Speaking ('en_GB'), u'focus mode'

I don't quite see what is happening but it looks like it never detects the fact that it needs to create a buffer until I press a key and make Firefox magically appear to nvda, which otherwise is confused.

@nvaccessAuto
Copy link
Author

Comment 11 by briang1 on 2015-01-23 22:50
Well, I can even get it to happen in Master, but not in the release version.
It is very erratic, and thus I suspect a timing issue. as the watchdog is nearly always being triggered, could it be that vital info is just sometimes missed when its locked up with the watchdog?
The question is, though why does it seemingly affect Firefox so badly, could it be that Firefox is not always sending the right info?

As for the other issue mentioned, I don't see that very much here.
Its not been a problem .
Its interesting though that it only requrires a cursor key to be pressed to make nvda wake up.

@jcsteh
Copy link
Contributor

jcsteh commented Jun 29, 2017

@Brian1Gaff, @MichelSuch, can you still reproduce this on non-XP systems?

@Brian1Gaff
Copy link

Brian1Gaff commented Jun 29, 2017 via email

@Brian1Gaff
Copy link

Brian1Gaff commented Jun 29, 2017 via email

@ehollig ehollig changed the title Firefox does not gain focus when started from xp with latest snapshots Firefox does not gain focus when started from Windows 7 with latest snapshots Aug 10, 2017
@LeonarddeR
Copy link
Collaborator

@Brian1Gaff: How about the most recent next snapshots that include #7535?

@Adriani90
Copy link
Collaborator

I suggest closing this in favor of #8389 and referenced issues because they are reproducible on Windows 7 and higher.

@Adriani90
Copy link
Collaborator

@LeonarddeR, @Brian1Gaff what do you think about my Suggestion above?

1 similar comment
@Adriani90
Copy link
Collaborator

@LeonarddeR, @Brian1Gaff what do you think about my Suggestion above?

@Adriani90
Copy link
Collaborator

I am closing this in favor of #8389 because this issue is very general and occurs in several situations regardless of the application. The discussion in that issue goes further and will continue there.

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

6 participants