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
NVDA crashes in Visual Studio 2010 Professional #1380
Comments
Attachment nvda crash.log added by ianr on 2011-02-19 18:14 |
Attachment nvda crash with debug.log added by ianr on 2011-02-21 20:45 |
Comment 1 by ianr on 2011-02-21 20:47 |
Attachment nvda crash.2.log added by ianr on 2011-02-23 12:44 |
Comment 2 by ateu on 2011-12-05 15:32 I have a friend which uses VS and he confirm this. NVDA stops reading an shows an error messaging. |
Could users of more recent versions of Visual Studio test and let us know if these frequent crashes with NVDA still take place? If not, I suggest closing this ticket as worksforme or invalid. |
@IanR is this issue still reproducible? |
@francipvb, @JulienCochuyt do you know by chance if this is still occuring in VS Studio 2010 or newer versions? This is a prety old issue and we lost contact to the initial author. |
I don't know. |
I haven't seen this issue in recent versions of Visual Studio. Given we seem to be unable to contact the original author, I'm closing this. |
Reported by ianr on 2011-02-19 18:13
Sometimes NVDA will crash while in VS 2010. I notice this when trying to move the cursor with the arrow keys and NVDA is no longer reading.
Generally Visual Studio will become unresponsive for about 30 seconds during which time I go to task manager and see that nvda is still running for the next 30 seconds or so, then it crashes and Visual Studio becomes responsive again.
This crashing generally happens between 5 and 10 times in an 8 hour period of using Visual Studio.
It also used to happen in older versions of nvda such as 2010.2 and 2010.1.
I have attached the log file taken from my %temp% folder.
Unfortunately log level was set to info at the time.
I will set my log level to debug and see if I can get a better log to attach.
The text was updated successfully, but these errors were encountered: