Vscode: VSCode hitting CPU

Created on 14 Jun 2020  路  11Comments  路  Source: microsoft/vscode




  • VSCode Version: 1.46.0
  • OS Version: Linux x64 4.15.0-106-generic
  • Hardware: CPU i5 8th gen, 16G RAM, SSD

Steps to Reproduce:

  1. Run just one instance of VSCode, on a react-scripts app, moderately large, with a few opened tabs, vscode will start hitting CPU when you edit code or save, it's gets really intense if you save invalid code

This problems happens gradually, maybe not just from latest version

I've made sure that node_modules/ and build/ directories are in my files.exclude, files.watcherExclude and search.exclude as I know this has been a problem in the past


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

needs more info

Most helpful comment

I have the same problem

All 11 comments

I have the same problem

Do you also see this when you disable all extensions?

To find out more about this issue, we need to get at the process that is causing the high load. VS Code creates multiple processes, each with different tasks.

When Code is consuming lots of CPU, please run "code --status" from the command line (or "code-insiders --status" if you are using VS Code Insiders edition).

Please attach the output of this command to this issue. Thanks!

When I go to Help > Open Process Explorer, things look calm though, processes are 0 or 1% CPU

I really confirm I'm running vscode with code --disable-extensions . (anyway, my only extension was code runner, not something that would use CPU constantly), shortly after my laptop fan will activate and keep running. If I close vscode, and run sublimetext on the same project, the fan goes silent again after a minute or so

The only other thing that can trigger the fans is google meet, I'd really like vscode to get back to something lighter, less intensive for the CPU

Please provide the information I requested in my previous comment:

To find out more about this issue, we need to get at the process that is causing the high load. VS Code creates multiple processes, each with different tasks.

When Code is consuming lots of CPU, please run "code --status" from the command line (or "code-insiders --status" if you are using VS Code Insiders edition).

Please attach the output of this command to this issue. Thanks!

@sandy081 Sorry I missed that code --status part

Here's what I get currently, the fan is running not too loud, it looks fine, but maybe there are still things I could improve or disable?

[25064:0618/143811.912441:ERROR:sandbox_linux.cc(369)] InitializeSandbox() called with multiple threads in process gpu-process.
Version:          Code 1.46.0 (a5d1cc28bb5da32ec67e86cc50f84c67cc690321, 2020-06-10T08:59:04.923Z)
OS Version:       Linux x64 4.15.0-106-generic
CPUs:             Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 x 1000)
Memory (System):  15.56GB (8.58GB free)
Load (avg):       2, 1, 1
VM:               0%
Screen Reader:    no
Process Argv:     --no-sandbox --disable-extensions
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
                  protected_video_decode:        unavailable_off
                  rasterization:                 disabled_software
                  skia_renderer:                 disabled_off_ok
                  video_decode:                  unavailable_off
                  viz_display_compositor:        enabled_on
                  viz_hit_test_surface_layer:    disabled_off_ok
                  webgl:                         enabled
                  webgl2:                        enabled

CPU %   Mem MB     PID  Process
    0      112   11037  code main
    0       32   11039     zygote
    0       80   11061     gpu-process
    0       48   11074     utility
    0      112   11290     shared-process
    0        0   25087       /bin/sh -c /bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
    0        0   25088         /bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
    0      319   23422     window (index.js - admin - Visual Studio Code)
    0      112   23451       extensionHost
    0       96   23539         electron_node tsserver.js 
    0     1291   23540         electron_node tsserver.js 
    0      127   23574           electron_node typingsInstaller.js typesMap.js 
    0       48   23646         /usr/share/code/code /usr/share/code/resources/app/extensions/json-language-features/server/dist/jsonServerMain --node-ipc --clientProcessId=23451
    0        0   23452       /bin/bash
    0       32   23614         npm
    0        0   23625           sh -c PORT=7300 react-scripts start
    0       32   23626             node /home/caub/dev/Storeganise/admin/node_modules/.bin/react-scripts start
    0      478   23633               node /home/caub/dev/Storeganise/admin/node_modules/react-scripts/scripts/start.js
    0       80   23521       watcherService
    0       48   23726       searchService

Workspace Stats: 
|  Window (index.js - admin - Visual Studio Code)
|    Folder (admin): 890 files
|      File types: js(560) less(39) scss(32) css(31) png(22) map(19) eot(8)
|                  svg(8) ttf(8) woff(8)
|      Conf files: settings.json(1) jsconfig.json(1) package.json(1)

after a while, CPU fan still running moderately

[28427:0618/150923.703686:ERROR:sandbox_linux.cc(369)] InitializeSandbox() called with multiple threads in process gpu-process.
Version:          Code 1.46.0 (a5d1cc28bb5da32ec67e86cc50f84c67cc690321, 2020-06-10T08:59:04.923Z)
OS Version:       Linux x64 4.15.0-106-generic
CPUs:             Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 x 984)
Memory (System):  15.56GB (9.04GB free)
Load (avg):       1, 1, 1
VM:               0%
Screen Reader:    no
Process Argv:     --no-sandbox --disable-extensions
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
                  protected_video_decode:        unavailable_off
                  rasterization:                 disabled_software
                  skia_renderer:                 disabled_off_ok
                  video_decode:                  unavailable_off
                  viz_display_compositor:        enabled_on
                  viz_hit_test_surface_layer:    disabled_off_ok
                  webgl:                         enabled
                  webgl2:                        enabled

CPU %   Mem MB     PID  Process
    0      112   11037  code main
    0       32   11039     zygote
    0       80   11061     gpu-process
    0       48   11074     utility
    0      112   11290     shared-process
    0        0   28452       /bin/sh -c /bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
    0        0   28453         /bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
    0      287   23422     window (index.js - admin - Visual Studio Code)
    0      127   23451       extensionHost
    0      112   23539         electron_node tsserver.js 
    8      797   23540         electron_node tsserver.js 
    0      127   23574           electron_node typingsInstaller.js typesMap.js 
    0       48   23646         /usr/share/code/code /usr/share/code/resources/app/extensions/json-language-features/server/dist/jsonServerMain --node-ipc --clientProcessId=23451
    0        0   23452       /bin/bash
    0       32   28206         npm
    0        0   28225           sh -c PORT=7300 react-scripts start
    0       32   28226             node /home/caub/dev/Storeganise/admin/node_modules/.bin/react-scripts start
    0      319   28233               node /home/caub/dev/Storeganise/admin/node_modules/react-scripts/scripts/start.js
    0       80   23521       watcherService
    0       48   23726       searchService

Workspace Stats: 
|  Window (index.js - admin - Visual Studio Code)
|    Folder (admin): 890 files
|      File types: js(560) less(39) scss(32) css(31) png(22) map(19) eot(8)
|                  svg(8) ttf(8) woff(8)
|      Conf files: settings.json(1) jsconfig.json(1) package.json(1)

Another project, with vscode running hard on the cpu

[990:0618/201417.989762:ERROR:sandbox_linux.cc(369)] InitializeSandbox() called with multiple threads in process gpu-process.
Version:          Code 1.46.0 (a5d1cc28bb5da32ec67e86cc50f84c67cc690321, 2020-06-10T08:59:04.923Z)
OS Version:       Linux x64 4.15.0-106-generic
CPUs:             Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 x 900)
Memory (System):  15.56GB (8.09GB free)
Load (avg):       1, 1, 1
VM:               0%
Screen Reader:    no
Process Argv:     --no-sandbox --disable-extensions
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
                  protected_video_decode:        unavailable_off
                  rasterization:                 disabled_software
                  skia_renderer:                 disabled_off_ok
                  video_decode:                  unavailable_off
                  viz_display_compositor:        enabled_on
                  viz_hit_test_surface_layer:    disabled_off_ok
                  webgl:                         enabled
                  webgl2:                        enabled

CPU %   Mem MB     PID  Process
    0      112    3647  code main
    0       32    3649     zygote
    0       80    3673     gpu-process
    0       48    3686     utility
    0      510    3697     window (auth.js - api - Visual Studio Code)
    0      175    3759       extensionHost
    0      143    3839         electron_node tsserver.js 
    0      861    3840         electron_node tsserver.js 
    0      112    3873           electron_node typingsInstaller.js typesMap.js 
    0       80    4106         /usr/share/code/code /usr/share/code/resources/app/extensions/json-language-features/server/dist/jsonServerMain --node-ipc --clientProcessId=3759
    0        0    3766       /bin/bash
    0       80    3821       watcherService
    0      112    3898     shared-process

Workspace Stats: 
|  Window (auth.js - api - Visual Studio Code)
|    Folder (api): 772 files
|      File types: js(470) json(18) html(10) jsx(9) ejs(4) css(2) _foo(1)
|                  env(1) eslintrc(1) gitignore(1)
|      Conf files: launch.json(1) settings.json(1) package.json(1)
|      Launch Configs: node

[5887:0619/153257.936498:ERROR:sandbox_linux.cc(369)] InitializeSandbox() called with multiple threads in process gpu-process.
Version:          Code 1.46.0 (a5d1cc28bb5da32ec67e86cc50f84c67cc690321, 2020-06-10T08:59:04.923Z)
OS Version:       Linux x64 4.15.0-106-generic
CPUs:             Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 x 892)
Memory (System):  15.56GB (11.38GB free)
Load (avg):       1, 1, 1
VM:               0%
Screen Reader:    no
Process Argv:     --no-sandbox --disable-extensions
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
                  protected_video_decode:        unavailable_off
                  rasterization:                 disabled_software
                  skia_renderer:                 disabled_off_ok
                  video_decode:                  unavailable_off
                  viz_display_compositor:        enabled_on
                  viz_hit_test_surface_layer:    disabled_off_ok
                  webgl:                         enabled
                  webgl2:                        enabled

CPU %   Mem MB     PID  Process
    0      112    1755  code main
    0       32    1757     zygote
    0       80    1778     gpu-process
    0       48    1792     utility
    0       96    1995     shared-process
    0        0    5910       /bin/sh -c /bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
    0        0    5911         /bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
    0      303    2037     window (unit-rental.js - api - Visual Studio Code)
    0      127    2062       extensionHost
    0      112    2143         electron_node tsserver.js 
    0      765    2144         electron_node tsserver.js 
    0       96    2178           electron_node typingsInstaller.js typesMap.js 
    0       80    4422         /usr/share/code/code /usr/share/code/resources/app/extensions/json-language-features/server/dist/jsonServerMain --node-ipc --clientProcessId=2062
    0        0    2063       /bin/bash
    0       80    2126       watcherService
    0       48    5553       searchService

Workspace Stats: 
|  Window (unit-rental.js - api - Visual Studio Code)
|    Folder (api): 775 files
|      File types: js(472) json(18) html(10) jsx(9) ejs(4) css(2) _foo(1)
|                  env(1) eslintrc(1) gitignore(1)
|      Conf files: launch.json(1) settings.json(1) package.json(1)
|      Launch Configs: node

@caub in your output I am not seeing any of VSCode processes take any CPU?

@bpasero correct, so I don't really know, could be the room temperature, but it's not really hot

I still observe that CPU fan starts running hard if I save invalid code, I guess tsserver isn't happy when this happens

@caub are you able to pin point it to the TS server or do you speculate on that?

it's just pure speculation, sorry

Ok, please update when you found out which process exactly is spending CPU cycles.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

Was this page helpful?
0 / 5 - 0 ratings