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

NVDA hangs up in terminal, when a large piece of text is loaded #6291

Open
dawidpieper opened this Issue Aug 22, 2016 · 17 comments

Comments

Projects
None yet
7 participants
@dawidpieper
Copy link

dawidpieper commented Aug 22, 2016

I know that normal user doesn't have this problem.
But developers, mainly developers working in terminal, could have.

When large piece of text is loaded to the terminal at the same time, for example, 10000 characters of more, NVDA is hanging up. Also, after a moment, the system hangs up.
The only way is to wait.
NVDA is not reading the text, it's reading pieces of text, then a moment of silence, different piece, silence...

For example, I can call this in ruby by writing

for i in 1..100000
print("A fragment number #{i.to_s} ")
end

Also, we can find this error, when we'll using in terminal app, which writes big pieces of text.
In console commands, like tree, we won't observe this eror, because it isn't loading of text at the same time, there's a while between printing new files.

What is interesting...
The problem is hanging up the all system, you can not open task manager or other apps.

Thank you for help
Greetings,
Dawid Pieper

@jcsteh

This comment has been minimized.

Copy link
Contributor

jcsteh commented Aug 22, 2016

What version and build of Windows are you using? We noticed severe performance problems with consoles in earlier builds of Windows 10, but this appears to be fixed in the anniversary update at least.

@dawidpieper

This comment has been minimized.

Copy link
Author

dawidpieper commented Aug 22, 2016

Thank you for you reply.
i'm using Windows 7 SP1 6.1.7601, but I had this problem on Windows 8.1 too, with all updates on May.
Regards,
DP
----- Original Message -----
From: James Teh
To: nvaccess/nvda
Cc: Dawid Pieper ; Author
Sent: Tuesday, August 23, 2016 12:19 AM
Subject: Re: [nvaccess/nvda] NVDA hangs up in terminal, when a large piece of text is loaded (#6291)

What version and build of Windows are you using? We noticed severe performance problems with consoles in earlier builds of Windows 10, but this appears to be fixed in the anniversary update at least.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@ctoth

This comment has been minimized.

Copy link

ctoth commented Aug 25, 2016

I have also observed this behavior.
Specifically when NVDA is set to speak typed characters, but I still also get it sometimes when this is not true. I often have to restart NVDA with the hotkey to get my system back.

@bhavyashah

This comment has been minimized.

Copy link

bhavyashah commented Aug 19, 2018

@dawidpieper @ctoth Do you still experience this freeze in the terminal (almost two years after the original report)?

@lukaszgo1

This comment has been minimized.

Copy link
Contributor

lukaszgo1 commented Dec 8, 2018

I can confirm, that this issue is still present on Windows 7 ad least. The only way to restore NVDA to it's working condition is to switch user with CTRL+Alt+Delete and kill NVDA process from the second account. Any chance of prioritizing this? To be honest when i have to work in terminal and I am suspecting, that big amount of text would be displayed I am switching to JAWS, because fighting with frozen NVDA is the last thing, which I want to do in the middle of my programming classes.

@lukaszgo1

This comment has been minimized.

Copy link
Contributor

lukaszgo1 commented Dec 13, 2018

@lukaszgo1

This comment has been minimized.

Copy link
Contributor

lukaszgo1 commented Dec 13, 2018

I am able to reproduce it 100% of the time with the c program attached. In the rare situations in which NVDA crashes softly enough to log anything the log contains
WARNING - watchdog.watcher (23:30:46.661):
Core frozen in stack:
File "nvda.pyw", line 227, in
File "core.pyc", line 516, in main
File "wx\core.pyc", line 2134, in MainLoop
File "gui_init
.pyc", line 985, in Notify
File "core.pyc", line 487, in run
File "queueHandler.pyc", line 86, in pumpAll
File "queueHandler.pyc", line 50, in flushQueue
File "comtypesMonkeyPatches.pyc", line 54, in newCpbDel
File "comtypes_init_.pyc", line 919, in del
File "comtypes_init_.pyc", line 1174, in Release
File "winConsoleHandler.pyc", line 142, in consoleWinEventHook
File "wincon.pyc", line 69, in GetConsoleScreenBufferInfo
6291.zip

The program attached is of course not very useful, but it demonstrates the issue pretty well.

@lukaszgo1

This comment has been minimized.

Copy link
Contributor

lukaszgo1 commented Jan 21, 2019

It happened again when installing a bunch of dependencies with Pip. Am I really the only one experiencing this?

@leonardder

This comment has been minimized.

Copy link
Collaborator

leonardder commented Jan 21, 2019

I recall I've seen this issue as well, and I have an idea to improve this, at least in such a way that you no longer have to fiddle with signing out and back in again.

@tspivey

This comment has been minimized.

Copy link
Contributor

tspivey commented Jan 21, 2019

You're not the only one. I'm used to it by now, and just alt tab out as fast as I can.
I don't think I've had to sign out in a while. Running your test program, NVDA freezes, but I can still press windows+m to go to the desktop and ALT+CTRL+n works to restart NVDA.

@leonardder

This comment has been minimized.

Copy link
Collaborator

leonardder commented Jan 21, 2019

Here is a branch that is very aggressive in ignoring input if the core is frozen. And there's a try build for that

@lukaszgo1

This comment has been minimized.

Copy link
Contributor

lukaszgo1 commented Jan 21, 2019

With this try build nVDA still freezes when executing my test program, but I am able to kill it with CTRL+ALT+D, so switching users is no longer required. Thanks @leonardder Any chance for fixing the freeze issue also?

@leonardder

This comment has been minimized.

Copy link
Collaborator

leonardder commented Jan 21, 2019

A, so it definitely fixes a major part, that's great. I will investigate further.

@leonardder

This comment has been minimized.

Copy link
Collaborator

leonardder commented Jan 21, 2019

Giving this a p2, since it tends to hang up the entire system.

@lukaszgo1

This comment has been minimized.

Copy link
Contributor

lukaszgo1 commented Jan 26, 2019

@leonardder I understand that properly fixing this would take a while, but would it be possible to include the fix from the try build above in master in the mean time?

@leonardder

This comment has been minimized.

Copy link
Collaborator

leonardder commented Jan 28, 2019

I think that makes sense, yes.

@leonardder

This comment has been minimized.

Copy link
Collaborator

leonardder commented Jan 29, 2019

Ugh, it wasn't my intention to have this automatically closed, as it isn't fixed entirely. Reopening.

@leonardder leonardder reopened this Jan 29, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.