Vscode: Integrated terminal very slow

Created on 13 Oct 2020  路  5Comments  路  Source: microsoft/vscode

Issue Type: Bug

Just after the most recent update, the Integrated terminal is extremely slow to display any text, either entering commands or displaying the stdout of commands.
Many times typing a complete command at the prompt will show up a s-i-n-g-l-e - c-h-a-r-a-c-t-e-r - a-t - a - t-i-m-e over several seconds after you finished typing.

It does not matter which Shell I use (PowerShell, CMD, WSL bash, Git Bash). Although, the bash shells seem to perform a little better.

All of these Shells perform normally on my computer, it is only when running in the Intergrated Terminal in VSCode.

Also, connecting to a remote computer with ssh, the stdout is also very slow. Again, no problems using in any Shell outside of VSCode.

Is there some setting and can change back?

VS Code version: Code 1.50.0 (93c2f0fbf16c5a4b10e4d5f89737d9c2c25488a3, 2020-10-07T06:10:52.432Z)
OS version: Windows_NT x64 10.0.18363


System Info

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz (4 x 2496)|
|GPU Status|2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
opengl: enabled_on
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|15.88GB (8.05GB free)|
|Process Argv|--crash-reporter-id f652528b-5678-4b12-9ca0-3de6b1e1135f|
|Screen Reader|no|
|VM|0%|

Extensions (7)

Extension|Author (truncated)|Version
---|---|---
better-toml|bun|0.3.2
macros|ged|1.2.1
graphviz-markdown-preview|gee|0.0.8
sftp|lix|1.12.9
marp-vscode|mar|0.15.1
python|ms-|2020.9.114305
rust|rus|0.7.8


integrated-terminal needs more info

Most helpful comment

changing the following settings helped. Not sure why an update would make the Integrated Terminal nearly unusable.

    "terminal.integrated.allowChords": false,
    "terminal.integrated.drawBoldTextInBrightColors": false,
    "terminal.integrated.experimentalLinkProvider": false,
    "terminal.integrated.rendererType": "auto"

All 5 comments

changing the following settings helped. Not sure why an update would make the Integrated Terminal nearly unusable.

    "terminal.integrated.allowChords": false,
    "terminal.integrated.drawBoldTextInBrightColors": false,
    "terminal.integrated.experimentalLinkProvider": false,
    "terminal.integrated.rendererType": "auto"

Using the Docker extension to view logs (around a 8000 lines) of a container would make not just the terminal but the entire VSCode editor laggy.
Setting "terminal.integrated.rendererType" from "dom" to "auto" did the trick. I had never touched that setting before.

Version: 1.50.1 (system setup)
Commit: d2e414d9e4239a252d1ab117bd7067f125afd80a
Date: 2020-10-13T15:06:15.712Z (3 days ago)
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.18362

@clayms could you try out "terminal.integrated.rendererType": "experimentalWebgl"? If you could capture a performance profile through the devtools performance tab (help > toggle dev tools) and upload it that would let us know if the main thread is being blocked and by what.

Hi @meganrogge, @Tyriar 馃憢

Is this issue closed because it is fixed? Or do you still need more info?

FWIW I have the same issue, which is only present when terminal.integrated.rendererType is set to dom. I don't believe I have changed that setting before.

Here's the performance profile from my machine.

Version: 1.51.0 (user setup)
Commit: fcac248b077b55bae4ba5bab613fd6e9156c2f0c
Date: 2020-11-05T18:18:23.642Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.19041

Profile-20201111T132351.zip

@testworksau the profile's interesting, not sure what could cause this apart from a Chromium issue (cc @deepak1556):

image

It looks different to the OP's issue, typically slow rendering like this in the terminal on Windows is due to this issue https://github.com/microsoft/vscode/issues/76548

Was this page helpful?
0 / 5 - 0 ratings