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

Crash dump after changing settings when sleep mode is set to true #4451

Closed
nvaccessAuto opened this issue Sep 11, 2014 · 13 comments
Closed

Crash dump after changing settings when sleep mode is set to true #4451

nvaccessAuto opened this issue Sep 11, 2014 · 13 comments

Comments

@nvaccessAuto
Copy link

Reported by norrumar on 2014-09-11 12:38
Hi, I don't know exactly when NVDA has crashed. I couldn't restart it and I have needed to restart the computer.
I have stored an app module setting sleep mode variable to true, cause in an application the cursor doesn't work properly otherwise. I wanted to test if this could be fixed changing settings of the review cursor, for instance: don't follow the system cursor.
Then NVDA has failed and a crytical error has been logged in nvda-old.log.
Thanks

@nvaccessAuto
Copy link
Author

Comment 1 by norrumar on 2014-09-11 12:47
Sorry, the crash dump file can't be attached since it appears empty.
Thanks.

@nvaccessAuto
Copy link
Author

Comment 2 by jteh on 2014-09-11 23:23
Can you please provide the exact steps you took? I don't quite follow your description regarding toggling settings. Also, are you able to reproduce this?

@nvaccessAuto
Copy link
Author

Comment 3 by norrumar (in reply to comment 2) on 2014-09-12 03:21
Replying to jteh:

Can you please provide the exact steps you took? I don't quite follow your description regarding toggling settings.

  1. I created an appModule for an application setting sleepMode to True.

  2. Withing this application, I deactivated sleep mode.

  3. I opened Cursor settings dialog, into Preferences menu, and made changes and accepted them.

    Also, are you able to reproduce this?

Unfortunately no.
Thanks.

@nvaccessAuto
Copy link
Author

Comment 4 by jteh on 2014-09-12 03:53
So the crash occurred when you pressed the OK button to dismiss the dialog?

If you can't reproduce it this way, I suspect the crash wasn't actually related to this, but I don't have any idea what would have caused it in that case.

@nvaccessAuto
Copy link
Author

Comment 5 by norrumar (in reply to comment 4) on 2014-09-12 14:19
Replying to jteh:

So the crash occurred when you pressed the OK button to dismiss the dialog?

If you can't reproduce it this way, I suspect the crash wasn't actually related to this, but I don't have any idea what would have caused it in that case.

Hi, I believe that I have reproduced the crash without the dialog. Perhaps it is related to an application. I was trying to start it. Generally I need to deactivate NVDA, since the program is loaded very slowly otherwise.
It seams that this application doesn't work well with JAWS, and I don't know how it works with other screen readers.
Now the minidump and log are here.
Thanks.

@nvaccessAuto
Copy link
Author

Attachment nvda_crash.dmp added by norrumar on 2014-09-12 14:20
Description:
Crash dump

@nvaccessAuto
Copy link
Author

Attachment nvda-old.log added by norrumar on 2014-09-12 14:22
Description:
Log file

@nvaccessAuto
Copy link
Author

Comment 6 by jteh on 2014-09-15 22:23
This looks disturbingly similar to the crash dump from #4455. I can't glean anything useful from either. :(

@nvaccessAuto
Copy link
Author

Comment 7 by mdcurran on 2014-09-15 23:00
Please list all the add-ons you have installed.

@nvaccessAuto
Copy link
Author

Comment 8 by norrumar (in reply to comment 7) on 2014-09-16 12:30
Replying to mdcurran:

Please list all the add-ons you have installed.

Hi Mick. Currently I have these add-ons:

  • TeamViewer.
  • OCR.
  • PlaceMarkers.

These are posted at
http://addons.nvda-project.org

Furthermore I use Ecobraille add-on, attached to ticket 4078.

But before (when NVDA crashed) I had also GoogleSpeechRecognition (now unusable) and I had problems when installing vocalizer driver without voices. I needed to uninstall NVDA, since keyboard almost couldn't be used, then I reinstalled it.
Thanks.

@bhavyashah
Copy link

@nvdaes Does the reported crash still occur? If so, could you please test this with all add-ons disabled and then share your findings?

@nvdaes
Copy link
Sponsor Contributor

nvdaes commented Aug 28, 2017

Hi @bhavyashah, I don't have this problem now. You can close this. Cheers

@ehollig
Copy link
Collaborator

ehollig commented Aug 28, 2017

Closing, as requested in #4451 (comment)

@ehollig ehollig closed this as completed Aug 28, 2017
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

4 participants