Re: NVDA crashing


Adriani Botez
 

I use java programs. Anyway, at least i could solve the java problem.

Von meinem iPhone gesendet

Am 09.11.2017 um 10:39 schrieb zahra <nasrinkhaksar3@gmail.com>:

if you dont use java programs, you dont need to install java access briedge!
hope that help, God bless you!

On 11/9/17, Brian's Mail list account via Groups.Io
<bglists=blueyonder.co.uk@groups.io> wrote:
I seem to have missed a lot of messages in this thread. What exactly are you

doing to get this lock up? It seems to be attempting to read a screen which

is not being recognised and getting into a loop.

Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "adriani.botez via Groups.Io"
<adriani.botez=googlemail.com@groups.io>
To: <nvda@nvda.groups.io>
Sent: Wednesday, November 08, 2017 10:42 PM
Subject: Re: [nvda] NVDA crashing


Here is what I get from debug. I guess that those oleacc.AccessibleObjects
appear because I have pressed some keys on my keyboard while NVDA was
frozen. But I might be wrong. So does anyone have a solution in mind? In
addition, how can I make java access bridge available? And what is the user

gesture map?

DEBUG - core.main (23:14:26.414):

initializing Java Access Bridge support

WARNING - core.main (23:14:26.414):

Java Access Bridge not available



Initializing input core

DEBUGWARNING - inputCore.InputManager.loadUserGestureMap (23:14:26.848):

No user gesture map



DEBUGWARNING - watchdog._watcher (23:14:37.453):

Trying to recover from freeze, core stack:

File "nvda.pyw", line 199, in <module>

File "core.pyo", line 396, in main

File "wx\_core.pyo", line 8657, in MainLoop

File "wx\_core.pyo", line 7952, in MainLoop

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

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

File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent

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

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

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



WARNING - watchdog._watcher (23:14:52.469):

Core frozen in stack:

File "nvda.pyw", line 199, in <module>

File "core.pyo", line 396, in main

File "wx\_core.pyo", line 8657, in MainLoop

File "wx\_core.pyo", line 7952, in MainLoop

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

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

File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent

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

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

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



WARNING - watchdog._watcher (23:15:07.484):

Core frozen in stack:

File "nvda.pyw", line 199, in <module>

File "core.pyo", line 396, in main

File "wx\_core.pyo", line 8657, in MainLoop

File "wx\_core.pyo", line 7952, in MainLoop

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

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

File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent

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

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

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



WARNING - watchdog._watcher (23:15:22.500):

Core frozen in stack:

File "nvda.pyw", line 199, in <module>

File "core.pyo", line 396, in main

File "wx\_core.pyo", line 8657, in MainLoop

File "wx\_core.pyo", line 7952, in MainLoop

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

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

File "IAccessibleHandler.pyo", line 756, in processForegroundWinEvent

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

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

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



DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.316):

oleacc.AccessibleObjectFromEvent with window 66140, objectID 2124 and
childID 0: [Error -2147467259] Unbekannter Fehler

DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.318):

oleacc.AccessibleObjectFromEvent with window 66140, objectID 2125 and
childID 0: [Error -2147467259] Unbekannter Fehler

DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.319):

oleacc.AccessibleObjectFromEvent with window 66140, objectID 2126 and
childID 0: [Error -2147467259] Unbekannter Fehler

DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.319):

oleacc.AccessibleObjectFromEvent with window 66130, objectID 109 and childID

0: [Error -2147467259] Unbekannter Fehler

DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.319):

oleacc.AccessibleObjectFromEvent with window 66140, objectID 2134 and
childID 0: [Error -2147467259] Unbekannter Fehler

DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.321):

oleacc.AccessibleObjectFromEvent with window 66140, objectID 2135 and
childID 0: [Error -2147467259] Unbekannter Fehler

DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (23:15:37.321):

oleacc.AccessibleObjectFromEvent with window 66140, objectID 2136 and
childID 0: [Error -2147467259] Unbekannter Fehler



Thank you for your suggestions.

Best
Adriani





--
we have not sent you but as a mercy to the entire creation.
holy quran, chapter 21, verse 107.
in the very authentic narration from prophet Mohammad is:
indeed, imam husayn is the beacon of guidance and the ark of salvation.
best website for studying islamic book in different languages
www.al-islam.org


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