vscode: Integrated terminal poor performance and freezing

VSCode Version:

Version: 1.25.0
Commit: 0f080e5267e829de46638128001aeb7ca2d6d50e
Date: 2018-07-05T13:11:58.697Z
Electron: 1.7.12
Chrome: 58.0.3029.110
Node.js: 7.9.0
V8: 5.8.283.38
Architecture: x64

Version: 1.26.0-insider
Commit: bd953248ad6a8e2f8896bfb78b3ae40e0fd47426
Date: 2018-07-06T05:17:37.386Z
Electron: 1.7.12
Chrome: 58.0.3029.110
Node.js: 7.9.0
V8: 5.8.283.38
Architecture: x64

OS Version: Windows 10 & Ubuntu 18.04

Steps to Reproduce:

Open the integrated terminal
Maximize the terminal
Start trying to type commands

Does this issue occur when all extensions are disabled?: Yes

The integrated terminal is freezing constantly and sometimes causing VS Code to take over 8GB of RAM and causing my entire system to become sluggish. I’ve seen this issue reported and claiming that version 1.24 would fix this but it hasn’t and now those threads have all been locked. #36913 #47196 #46954

On the insiders version it seems to at least only freeze the terminal window itself, but this has basically made the terminal unusable for me. 🙁

I’d also like to note that keeping the terminal small minimizes the performance impact but is still noticeably sluggish

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 14
Comments: 42 (9 by maintainers)

Most upvoted comments

Well it’s definitely looking like it’s a 4K monitor problem, I’ll see if I can get my hands on one

+11

Tyriar on Aug 8, 2018

I have been experiencing this since upgrading to 1.24 and still having it at 1.25:1 (upgraded on July 11, 2018). None of the previously recommended fixes solved this problem.

code --status

Version:          Code 1.25.1 (1dfc5e557209371715f655691b1235b6b26a06be, 2018-07-11T15:43:53.668Z)
OS Version:       Windows_NT x64 10.0.17134
CPUs:             Intel(R) Xeon(R) CPU E5-2623 v4 @ 2.60GHz (8 x 2594)
Memory (System):  31.92GB (25.28GB free)
VM:               0%
Screen Reader:    no
Process Argv:     C:\Program Files\Microsoft VS Code\Code.exe
GPU Status:       2d_canvas:                    enabled
                  flash_3d:                     enabled
                  flash_stage3d:                enabled
                  flash_stage3d_baseline:       enabled
                  gpu_compositing:              enabled
                  multiple_raster_threads:      enabled_on
                  native_gpu_memory_buffers:    disabled_software
                  rasterization:                disabled_software
                  video_decode:                 enabled
                  video_encode:                 enabled
                  vpx_decode:                   enabled
                  webgl:                        enabled
                  webgl2:                       enabled
CPU %   Mem MB     PID  Process
    0       87   38708  code main
    0      133     476     gpu-process
    0       78   30784     shared-process
    0       55   35812     window (undefined)
    0      286   40828     window (Preview How to Code this App.md - REACT - Visual Studio Code)
    0       36   38556       searchService
    0      107   39196       extensionHost
    0       33   41364       terminal
    0        6   44652         winpty-process
    0        5   42060           "C:\Program Files\Git\bin\bash.exe"
    0       10   42528             "C:\Program Files\Git\bin\..\usr\bin\bash.exe"
    0        9   45208           console-window-host (Windows internal process)
    0       11   42808       electron-crash-reporter
    0       14   42844       watcherService
    0       10   41976         console-window-host (Windows internal process)
Workspace Stats:
|  Window (Preview How to Code this App.md - REACT - Visual Studio Code)
|    Folder (REACT): 192 files
|      File types: js(63) css(31) json(30) html(18) md(11) gitignore(10)
|                  svg(10) ico(10) jpg(9)
|      Conf files: package.json(10)

WhiskeyRomeoLima on Jul 20, 2018

I’m also having this issue on a new Dell XPS laptop I got yesterday. I wanted to share that downgrading my laptop’s resolution from 4K to 1080p solves the slugginesh / crashing completely, but it looks less sharp, so I wish there was another solution.

I tried changing the renderer type to dom, which does help diminish the crashes, but the response time when typing is much slower.

angel-urena on Aug 6, 2018

Another workaround that may work: code --ignore-gpu-blacklist

Thanks @Tyriar, this works for me. Changing terminal.integrated.rendererType back to canvas now makes the Terminal as fast as before. 👍

mhoyer on Aug 22, 2018

For what it’s worth I also experience sudden performance drop after a while when using integrated terminal on my Dell XPS 15 9560 w/ 4K display. Most noticed when using Powershell integrated terminal from the extention (probably because it’s the one I use the most on daily basis). I’ve noticed that when having just vscode and chrome open, when it suddenly starts lagging Chrome lags as well with the scrolling. Closing both apps and reopening Chrome make scroll smooth again. Both my GPU drivers are up to date with latest from Intel and nvidia. After reading this https://communities.intel.com/thread/119093 I’ve tryed disabling the nvidia GPU to prevent the current discret GPU issue, it seems to be less sensitive to falling in lag state. Not a solution though…

DjavanRoa on Aug 21, 2018

Another workaround that may work: code --ignore-gpu-blacklist

Tyriar on Aug 20, 2018

That seems to have stopped it from crashing @Tyriar, but rendering is now quite slow. I’ve never had to do this with previous version of VS Code FWIW.

jpayne on Jul 11, 2018

I will try using the DOM renderer once I get back home. However, I do know that I am using the latest graphics drivers available from Nvidia.

phil-harmoniq on Jul 9, 2018

I haven’t updated my drivers in a while, so I’ll give that a shot. --disable-gpu seemed to make it better so I guess it’s that.

Southclaws on Jul 9, 2018