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

Automatic updates starting with snapshot 5931 result in the following error: "Error registering focus winEvent hook OK." #3066

Closed
nvaccessAuto opened this issue Mar 9, 2013 · 3 comments

Comments

@nvaccessAuto
Copy link

@nvaccessAuto nvaccessAuto commented Mar 9, 2013

Reported by ppatel on 2013-03-09 14:38
Starting with snapshot 5931, automatic updates result in "Error registering focus winEvent hook OK"error. NVDA appears to update but does not actually do so. NVDA.log does not appear to show any error. System: Win 7, 64 bit; running Nuance speech. The error has continued to occur in snapshot 5932 and this morning in snapshot 5935. I will download the full executable to remove the error if possible.

@nvaccessAuto

This comment has been minimized.

Copy link
Author

@nvaccessAuto nvaccessAuto commented Mar 9, 2013

Comment 1 by ppatel on 2013-03-09 17:00
The full executable also had the same error twice; but appeared to update once the OK button was hit each time. Just to be certain, I restarted the machine and ran the update. The error did not occur after restarting Windows.

@nvaccessAuto

This comment has been minimized.

Copy link
Author

@nvaccessAuto nvaccessAuto commented Mar 10, 2013

Comment 2 by mdcurran on 2013-03-10 23:19
I'm pretty sure this is simply just a limitation of Windows. Either you'd been running without a reboot for quite some time (weeks?) or perhaps you started/restarted one or more ATs 100s of times. But in short, Windows ran out of resources to register for MSAA events.
If you see the issue again, please reopen.

Changes:
Added labels: cantfix
State: closed

@nvaccessAuto

This comment has been minimized.

Copy link
Author

@nvaccessAuto nvaccessAuto commented Mar 10, 2013

Comment 3 by ppatel (in reply to comment 2) on 2013-03-10 23:39
I wonder if there is a graceful way to let the user know about this issue not affecting the update. Based on this explanation, the error showing up is a usability issue. The explanation helps me understand what might have happened. How does the user interacting with the update in the moment know what to do?

Replying to mdcurran:

I'm pretty sure this is simply just a limitation of Windows. Either you'd been running without a reboot for quite some time (weeks?) or perhaps you started/restarted one or more ATs 100s of times. But in short, Windows ran out of resources to register for MSAA events.

If you see the issue again, please reopen.

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

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.