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

NVDA causes audio to fail in Win7 64 bit #686

Closed
nvaccessAuto opened this issue Jun 1, 2010 · 17 comments
Closed

NVDA causes audio to fail in Win7 64 bit #686

nvaccessAuto opened this issue Jun 1, 2010 · 17 comments
Labels
bug

Comments

@nvaccessAuto
Copy link

Reported by Rughead on 2010-06-01 07:41
On HP E9220Y with AMD Phenon2 quad core, NVDA randomly stops speaking from time to time. I have to usually reboot to get NVDA to work again in most cases. All other sounds on computer stop working at this point. Even JAWS will not launch when this happens. Sometimes I can unload NVDA, at which system sounds will come back. This problem occurs in all kinds of situations. Sometimes when only arrowing up and down in an HTML or txt document. It has even happened a few times while filling out this form. NVDA seems to work fine on my XP Pro system, but only has this problem on my Win7 64 bit system. Here is a copy of the log file when this last happened:
INFO - nvda (22:59:03):
Starting NVDA
INFO - core.main (22:59:04):
Config dir: C:\Users\CLH 2990\AppData\Roaming\nvda
INFO - config.save (22:59:08):
Configuration saved
INFO - core.main (22:59:08):
NVDA version 2010.1
INFO - core.main (22:59:08):
Using Windows version (6, 1, 7600, 2, '')
INFO - core.main (22:59:08):
Using Python version 2.6.4 (r264:75708, Oct 26 2009, 08:23:19) v.1500 32 bit (Intel)
INFO - core.main (22:59:08):
Using comtypes version 0.6.2
INFO - synthDriverHandler.setSynth (22:59:15):
Loaded synthDriver eloquence
INFO - core.main (22:59:15):
Using wx version 2.8.10.1 (msw-unicode)
INFO - braille.initialize (22:59:15):
Using liblouis version 1.8.0
INFO - braille.BrailleHandler.setDisplayByName (22:59:15):
Loaded braille display driver noBraille
INFO - core.main (22:59:16):
NVDA initialized
ERROR - unhandled exception (23:04:03):
Traceback (most recent call last):
File "virtualBuffers__init__.pyo", line 224, in
File "virtualBuffers__init__.pyo", line 454, in onAction
File "textInfos\offsets.pyo", line 257, in copy
File "virtualBuffers__init__.pyo", line 83, in init
File "textInfos\offsets.pyo", line 218, in init
File "virtualBuffers__init__.pyo", line 104, in getStoryLength
WindowsError: 1775 A null context handle was passed from the client to the host during a remote procedure call
ERROR - scriptHandler.executeScript (23:10:45):
error executing script: <bound method Gecko_ia2.script_activatePosition of <virtualBuffers.gecko_ia2.Gecko_ia2 object at 0x0704AFD0>> with key (None, 'return')
Traceback (most recent call last):
File "scriptHandler.pyo", line 100, in executeScript
File "virtualBuffers__init_.pyo", line 670, in script_activatePosition
File "virtualBuffers__init__.pyo", line 624, in activatePosition
File "virtualBuffers__init_.pyo", line 794, in shouldPassThrough
AttributeError: 'NoneType' object has no attribute 'states'
@nvaccessAuto
Copy link
Author

Attachment NVDALog.txt added by Rughead on 2010-06-01 07:45
Description:
NVDA log

@nvaccessAuto
Copy link
Author

Attachment 6-8-2010nvda.log added by Rughead on 2010-06-09 16:13
Description:
another log from when speech stops

@nvaccessAuto
Copy link
Author

Comment 2 by jteh on 2011-05-09 02:40
Another user has experienced this as well using a Sennheiser USB headset. In his case, it only failed soon after 2 hours. For this user, disabling progress bar beeps seemed to fix the issue.

Apparently, System Access had a similar issue a while back, but doesn't any longer.

Unfortunately, I don't really understand what could be causing this. We always open the audio device for tones even if progress bar beeps are disabled, so it's not just opening the audio device. That doesn't make any sense when correlated with the 2 hour wait before the issue occurs, although the original reporter didn't note any such wait.

@nvaccessAuto
Copy link
Author

Comment 3 by jteh on 2011-05-09 02:41
Changes:
Changed title from "NVDA stops working in Win7 64 bit" to "NVDA causes audio to fail in Win7 64 bit"

@nvaccessAuto
Copy link
Author

Comment 4 by nvdakor on 2014-12-12 06:12
Hi,
Coming back to this one...
To the original poster: could you try with NvDA 2014.4 to see if it is fixed? Thanks.

@nvaccessAuto
Copy link
Author

Comment 5 by briang1 on 2014-12-12 11:05
Well, for the record, I've just started to use a machine with 7 and 64bit versions of programs, and as yet have had no issues with sound going away. I seem to recall from the time these issues were going on, there was a suspicion that it was driver related and also might have something to do with the size of a file Windows created for temp use for sound. There have been updates of drivers and other windows patches since, so it might in fact be sorted now.

@LeonarddeR
Copy link
Collaborator

Last report of this seems to date from 6 years ago. Unless someone knows about similar issues, I think this can be closed.

@fernando-jose-silva
Copy link

I have this problem and I am using nvda next 14019 and windows 7 64bits.
What I can help, I'm at ease.

@ehollig
Copy link
Collaborator

ehollig commented Jul 12, 2017

Could #1710 be related?

@fernando-jose-silva
Copy link

fernando-jose-silva commented Jul 12, 2017 via email

@LeonarddeR LeonarddeR mentioned this issue Jul 17, 2017
Closed
@ehollig
Copy link
Collaborator

ehollig commented Oct 31, 2017

@fernando-jose-silva, are you still experiencing this issue or can this issue be closed?

@fernando-jose-silva
Copy link

I still have this problem, I also reported in the 1710.
If the nvda is with any beeps the sound hangs, if you disable the beeps the sound works.
This occurs on windows 7 64bits, on machines with windows 10 no.

@Brian1Gaff
Copy link

Brian1Gaff commented Nov 1, 2017 via email

@Adriani90
Copy link
Collaborator

Adriani90 commented Jul 28, 2018 •
edited

I think this is machine specific, we had some discussions on Gitter with @jcsteh and @dglee42 but we need a valuable log file to see where the problem actually comes from.

@ehollig
Copy link
Collaborator

ehollig commented Aug 15, 2018

@fernando-jose-silva, according to #686 (comment) we think this is machine specific. To verify this, we need a valuable log file to see where the problem actually comes from.

@fernando-jose-silva
Copy link

fernando-jose-silva commented Aug 15, 2018 via email

@josephsl
Copy link
Collaborator

Hi,

I see. Please reopen this issue if anyone experiences this in the future. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@LeonarddeR @josephsl @nvaccessAuto @Brian1Gaff @fernando-jose-silva @ehollig @Adriani90