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
CRITICAL CRASH WITH NVDA AND WORD 2016 #5954
Comments
Are you absolutely certain this is caused by NVDA? For example, can you
reproduce it if you use Narrator? Also, are you running Windows 10
Insider builds?
We have reason to believe there might be a bug in a recent update to
Word 2016 and/or Windows 10 that might be causing this.
|
Testing both with fresh instances of word exclusively with Narrator, For reference, I am running Windows 10 Home 64 bit version 1511 build On 16/05/2016 08:45, James Teh wrote:
|
Are you seeing some sort of crash dialog or is it more like a freeze where it stops responding? CC @michaelDCurran. |
I am getting an ANR dialog. "Microsoft Word has stopped working". On 16/05/2016 15:52, James Teh wrote:
|
I occasionally get this on windows 7 with older versions of word. It is very Brian bglists@blueyonder.co.uk I am getting an ANR dialog. "Microsoft Word has stopped working". On 16/05/2016 15:52, James Teh wrote:
You are receiving this because you are subscribed to this thread. |
No. It is the latest stable Windows 10 with the latest stable Word 2016 I tried using a (portable) copy of NVDA 2016.1, and word ran fine, and In case it's useful, I've copied the error log below.
On 16/05/2016 17:51, Brian1Gaff wrote:
|
Was your master-13324,b0e35d32) a portable or installed copy? if Thanks On 23/05/2016 8:39 AM, Thomas Cowley wrote:
Michael Curran |
It was an installed copy. I tested with a portable copy with my preferences saved, and a portable On 23/05/2016 08:44, Michael Curran wrote:
|
This is probably not the case, but do you have a messaging app called On 23/05/2016 2:46 PM, Thomas Cowley wrote:
Michael Curran |
No. On 23/05/2016 15:58, Michael Curran wrote:
|
Just a note that this problem still persists with NVDA 2016.2. It was I am going to try and see if it is one of my addons or programs doing On 23/05/2016 15:58, Michael Curran wrote:
|
I'm having the same, or at least a very similar issue here. Word 2010 64 bits on Windows 10 (normal release, no insider build), NVDA next-13326,62282e0b. I was editing a document and after a while NVDA freezes completely. When I restart NVDA, Word has gone in the "is not responding" state. A friend called earlier today, she has exactly the same issue with NVDA 2016.2. The not so helpful log output during the crash: DEBUGWARNING - watchdog._watcher (23:55:15): |
Just tried to reproduce the crash running from source commit 8b4b002. I typed for a while in the same document, but I couldn't get NVDA/Word to crash. |
It's very intermittent Sent from a mobile device.
|
It should be noted that several times this is happened to me while I've told Nvidia to create a dump for word and have never gotten it to produce one Sent from a mobile device.
|
Although this is most likely caused by support for grammar errors #5877, due to some implementation details, it won't be enough to just disable reporting of grammar errors. If testing with speech, you will need to disable Play Sounds for spelling errors, and if testing with braille, you will need to disable report spelling errors and disable report grammar errors. |
For people experiencing crashes in MS Word with NVDA, please run the following NVDA try build: This try build is equivalent to NVDA 2016.2, with out support for grammar errors in Microsoft Word, and also contains the fix for the Microsoft Word 2007 start-up crash on XP. Before running this build, it is very important that you reboot your computer to ensure that Microsoft word is not running, and to ensure it has not left anything around in memory. Once rebooted, start this build as a portable or installed copy, and only then open Microsoft Word. Please let us know if the crash goes away, or if it remains. Thanks |
Sorry, I mean to ensure that Microsoft word is still not running. The reboot ensures that Microsoft Word is started fresh when testing. Mick On 10/06/2016 1:53 PM, derekriemer wrote:
Michael Curran |
I didn't read this carefully, and heard remove rather than reboot. My bad. On 6/9/2016 9:57 PM, Michael Curran wrote:
Websites: email me at derek.riemer@colorado.edu mailto:derek.riemer@colorado.edu |
I have done as directed, and have not experienced any further crashing. Thanks. On Thu, Jun 9, 2016 at 10:58 PM, derekriemer notifications@github.com
Cordially, Nimer Jaber Please take the time to read this signature completely as it contains The message above is intended for the recipient to whom it was Registered Linux User 529141. To find out about a free and versatile screen reader for windows XP You can follow @nimerjaber on Twitter for the latest technology news. To contact me, you can reply to this email or you may call me at (218) |
Fix included in NVDA 2016.2.1, which was released a few hours ago. |
Hi, i'm sorry, that it happened for some users. anyway reporting of grammer errors and "playing sounds on spelling errors" was a great feature and on win7 32-bit and word 2010 it worked without problems. now i'm trying to reproduce on latest stable win10 and it seems that i cannot find no problem, so i hope, that this feature will be included again. |
Note that only reporting of grammar errors was removed. Alerts for spelling errors while typing still works and is still included.
Unfortunately, we have no idea how to work around this problem with grammar errors in Word, so it's unlikely we'll be able to bring this back any time soon..
|
Do we have any information about office vs. windows combinations where this issue does not occur? I've worked with Windows 10 and office 2016 multiple times and as far as I remember, haven't experienced crashes so far. May be we can enable the feature in working cases and disable it in others? |
Even where it does occur, it's intermittent. Also, it seems to happen faster/more often on some systems than others. I was eventually able to reproduce on Windows 10 with Office 2016, but it takes a lot of rapid typing for quite a while to trigger it.
|
It does. But sometimes my word was crashing when I opened a document and On 11/06/2016 17:33, James Teh wrote:
|
NVDA Version: master-13321,7b0fd6f5 causes Word 2016 to crash after typing for a short while. Turning off reporting of grammar errors does not fix this, so I don't think it is that feature causing the crash.
Word 2016, Office 365
The text was updated successfully, but these errors were encountered: