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

Apparent nvda error in installer #824

Closed
nvaccessAuto opened this issue Aug 10, 2010 · 2 comments
Closed

Apparent nvda error in installer #824

nvaccessAuto opened this issue Aug 10, 2010 · 2 comments

Comments

@nvaccessAuto
Copy link

Reported by briang1 on 2010-08-10 19:56
Note this ticket raised in case others think this is an error in the installer.

The log is from snap 95. The watchdog consistently thinks the core is frozen when loading the nvda installer on three machines. Only you know what the installer is doing after the sound has played but before the onscreen output is voiced. Partial log...

DEBUG - appModuleHandler.AppModule.loadKeyMap (20:08:01):
added 81 bindings to appModule <default (appName nvda_snapshot_main-3699_installer, process ID 3004) at address 22f2db0> from file .\appModules_default_desktop.kbd
DEBUGWARNING - watchdog.watcher (20:08:01):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 139, in
File "core.pyc", line 247, in main
File "wx_core.pyc", line 8007, in MainLoop
File "wx_core.pyc", line 7303, in MainLoop
File "core.pyc", line 232, in Notify
File "IAccessibleHandler.pyc", line 828, in pumpAll
File "IAccessibleHandler.pyc", line 644, in processFocusWinEvent
File "IAccessibleHandler.pyc", line 533, in winEventToNVDAEvent
File "NVDAObjects\IAccessible__init
.pyc", line 35, in getNVDAObjectFromEvent
File "IAccessibleHandler.pyc", line 361, in accessibleObjectFromEvent

DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (20:08:03):
Window 984026 dead or not responding: 1460 This operation returned because the timeout period expired.
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (20:08:05):
Window 852900 dead or not responding: 1460 This operation returned because the timeout period expired.
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (20:08:08):
Window 852900 dead or not responding: 1460 This operation returned because the timeout period expired.
DEBUGWARNING - watchdog.watcher (20:08:11):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 139, in
File "core.pyc", line 247, in main
File "wx_core.pyc", line 8007, in MainLoop
File "wx_core.pyc", line 7303, in MainLoop
File "core.pyc", line 232, in Notify
File "IAccessibleHandler.pyc", line 828, in pumpAll
File "IAccessibleHandler.pyc", line 738, in processForegroundWinEvent
File "IAccessibleHandler.pyc", line 533, in winEventToNVDAEvent
File "NVDAObjects\IAccessible__init
_.pyc", line 35, in getNVDAObjectFromEvent
File "IAccessibleHandler.pyc", line 361, in accessibleObjectFromEvent

DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (20:08:13):
Window 852900 dead or not responding: 1460 This operation returned because the timeout period expired.
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (20:08:15):
Window 852900 dead or not responding: 1460 This operation returned because the timeout period expired.
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (20:08:17):
Window 984026 dead or not responding: 1460 This operation returned because the timeout period expired.
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (20:08:19):
Window 984026 dead or not responding: 1460 This operation returned because the timeout period expired.
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (20:08:21):
Window 852680 dead or not responding: 1460 This operation returned because the timeout period expired.
ERROR - watchdog.watcher (20:08:21):
Core frozen in stack:
File "nvda.pyw", line 139, in
File "core.pyc", line 247, in main
File "wx_core.pyc", line 8007, in MainLoop
File "wx_core.pyc", line 7303, in MainLoop
File "core.pyc", line 232, in Notify
File "IAccessibleHandler.pyc", line 842, in pumpAll
File "IAccessibleHandler.pyc", line 602, in processGenericWinEvent
File "IAccessibleHandler.pyc", line 533, in winEventToNVDAEvent
File "NVDAObjects\IAccessible__init
_.pyc", line 35, in getNVDAObjectFromEvent
File "IAccessibleHandler.pyc", line 361, in accessibleObjectFromEvent

DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (20:08:23):
Window 852680 dead or not responding: 1460 This operation returned because the timeout period expired.
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (20:08:23):
Window 852680 dead or not responding: 6 The handle is invalid.
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (20:08:23):
Window 983742 dead or not responding: 6 The handle is invalid.
IO - speech.speakText (20:08:25):
Speaking u'NVDA Setup dialog Another copy of NVDA is already running. It will be shut down before the installer can continue.'
IO - speech.speakText (20:08:25):
Speaking u'OK button'
IO - keyboardHandler.internal_keyDownEvent (20:08:35):
key press: control+alt+r
INFO - core.main (20:08:35):
Exiting....

The question of course, is.. is this real or not?

Well..
DEBUG - appModuleHandler.AppModule.loadKeyMap (20:23:06):
added 81 bindings to appModule <_default (appName nvda_snapshot_main-3699_installer, process ID 1660) at address 2305b70> from file .\appModules_default_desktop.kbd
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (20:23:08):
Window 1246000 dead or not responding: 1460 This operation returned because the timeout period expired.
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (20:23:10):
Window 918308 dead or not responding: 1460 This operation returned because the timeout period expired.
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (20:23:13):
Window 918308 dead or not responding: 1460 This operation returned because the timeout period expired.
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (20:23:15):
Window 918308 dead or not responding: 1460 This operation returned because the timeout period expired.
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (20:23:17):
Window 918308 dead or not responding: 1460 This operation returned because the timeout period expired.
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (20:23:19):
Window 1246000 dead or not responding: 1460 This operation returned because the timeout period expired.
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (20:23:21):
Window 1246000 dead or not responding: 1460 This operation returned because the timeout period expired.
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (20:23:23):
Window 2163472 dead or not responding: 1460 This operation returned because the timeout period expired.
IO - speech.speakText (20:23:25):
Speaking u'NVDA Setup dialog Another copy of NVDA is already running. It will be shut down before the installer can continue.'
IO - speech.speakText (20:23:25):
Speaking u'OK button'
IO - keyboardHandler.internal_keyDownEvent (20:23:30):
key press: control+alt+r
INFO - core.main (20:23:30):
Exiting
Ok, that was with watchdog disabled.
And it did not lock up as such.
Now clearly something is going on, but in fact this seems to be a lot of disc access, which I suppose stops other threads, making the watchdog think its all gone badly wrong, when in fact it has not.
The timings for the two are not much different, but the first creates the error.
And no, my disc access is dma if available, not pio only..
Not really a defect as such, but hopefully useful info from a single core machine or 2 or 3.

Maybe the timer needs to be a bit longer than 10?
I do realise that this error does no actual harm, of course!

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2010-08-10 21:28
When you say it hasn't gone badly wrong, I think you may be misunderstanding the error. The error is meant to indicate that NVDA's main thread has blocked (frozen), nothing more. In an ideal world, NVDA wouldn't stop responding even when there is a lot of other system activity. I think you'll find that while this activity is going on, NVDA commands such as NVDA+f12 to read the time won't work, which indicates that NVDA isn't responding. In this case, the installer is so busy that it can't respond to NVDA's queries at all, hence the freeze.

I don't think there is anything we can do about this particular freeze at the moment.

@nvaccessAuto
Copy link
Author

Comment 2 by jteh on 2010-08-18 00:13
2729476 changes this log message to a warning instead of an error.
Changes:
State: closed

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

1 participant