-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Integrated Terminal is slow when wrapping very long line #102705
Comments
+1 same exact issue here, any very long line printed to the integrated terminal sends 1 thread to 100% and locks up the entire IDE if any attempt to scroll back in the terminal pane is made. I experience this on:
|
/duplicate #74620 |
@Noh3choo you might be using the dom renderer, try this setting |
@Tyriar, it is still failing with |
@crystalin your issue is likely the Windows-specific #74620 |
I don’t think it is, this is a recent regression and not a duplicate. I am not using the DOM renderer and setting experimentalWebgl has not affect on the bug. |
@Noh3choo on Linux if you have problems scrolling, it's renderer related. You can try launching with |
Thanks Tyriar, I have tried all of your suggestions and none change the behavior. |
Steps to Reproduce:
This issue appears with
--disable-extensions
also with--disable-gpu
or with any choice ofterminal.integrated.rendererType
.This issue is independent of the shell (powershell, cmd, wsl.... all have the issue)
VsCode also freezes when the terminal freezes (If the line is very long, it might trigger notification to "kill or wait vscode")
During the freeze, CPU is at around 10% (high considering there are 8/16 cores), GPU at 0%
Keeping the terminal visible (without any changes in its content) makes VSCode slow. The more of the lines is displayed, but also the longer the text is (outside of the visible area), the slower it gets.
Hiding the terminal by switching to another one restore the UI responsiveness to the normal.
I suspect this is related to the computation of the line wrap.
The text was updated successfully, but these errors were encountered: