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

Jump to bottom

Closeing nvda and opening system access causes skype 5 to crash #1010

Closed
nvaccessAuto opened this issue Nov 1, 2010 · 2 comments
Closed

Closeing nvda and opening system access causes skype 5 to crash #1010

nvaccessAuto opened this issue Nov 1, 2010 · 2 comments
Labels
bug close/worksforme

Comments

@nvaccessAuto
Copy link

Reported by mike.reiser on 2010-11-01 06:24
With skype 5, closeing nvda and starting System Access causes Skype to either hang and stop responding, or produce the standard "The instruction at xxxxxx can not be read" message. STR:

  1. With Skype running, close nvda and either bring up System Access if you have it or load http://www.satogo.com.
  2. Log in and load System Access.

Shortly after System Access loads, skype crashes. This doesn't seem to happen when switching from System Access to nvda, which seems to make me think that something with nvda might be causeing the issue. Expected results: Skype should behave normally.

Actual results: Skype exhibits the behavior noted above.
@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2010-11-01 06:31
Debugging this is going to be fairly difficult. While this is probably due to NVDA leaving some code behind because it couldn't unload for some reason, this doesn't necessarily mean that our code is the actual cause of the crash (although I'm not saying that isn't the case).
Changes:
Milestone changed from None to None

@dkager
Copy link
Collaborator

dkager commented Jul 18, 2017

Can't reproduce with Skype 7 and SAToGo.

@dkager dkager closed this as completed Jul 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug close/worksforme
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dkager @nvaccessAuto