-
-
Notifications
You must be signed in to change notification settings - Fork 784
Performance regressions in NVDA with Windows Terminal #14189
Copy link
Copy link
Closed
Labels
app/windows-terminalNew terminal app, potentially supersedes app/windows-console (repo: microsoft/terminal)New terminal app, potentially supersedes app/windows-console (repo: microsoft/terminal)bug/regressionclose/works-for-meneeds-technical-investigationA technical investigation is required to progress the issue.A technical investigation is required to progress the issue.p4https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityperformancetriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Metadata
Metadata
Assignees
Labels
app/windows-terminalNew terminal app, potentially supersedes app/windows-console (repo: microsoft/terminal)New terminal app, potentially supersedes app/windows-console (repo: microsoft/terminal)bug/regressionclose/works-for-meneeds-technical-investigationA technical investigation is required to progress the issue.A technical investigation is required to progress the issue.p4https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityperformancetriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Type
Fields
Give feedbackNo fields configured for issues without a type.
/CC @codeofdusk
Steps to reproduce:
Use Windows Terminal. In particular:
Basically normal use of the terminal
Actual behavior:
I've noticed that NVDA now lags noticeably:
Expected behavior:
None of this should be happening, unsure if it s aregression with NVDA or Terminal
NVDA logs, crash dumps and other attachments:
None
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
alpha-26524,bc1f92f9 (2022.4.0.26524)
Windows version:
10.0.19044.2006
Name and version of other software in use when reproducing the issue:
Windows terminal 1.14.2281.0
Other information about your system:
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
I have also seen this on another laptop which is on a more recent alpha build
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?