CPU usage 100% in Ubuntu 16.04

[mjbvz]

From Cristian Flores (@critical) on April 12, 2018 7:1

Issue Type: Bug

Running VSCode I have 100% of CPU usage from electron_node electronForkStart.js tsserver.js process
Same behaviour starting with or without --disable-extentions flag

This is output from code --status:

Version: Code 1.22.1 (950b8b0d37a9b7061b6f0d291837ccc4015f5ecd, 2018-04-06T00:24:49.616Z)
OS Version: Linux x64 4.13.0-38-generic
CPUs: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (4 x 3499)
Memory (System): 15.58GB (2.90GB free)
Load (avg): 2, 2, 2
VM: 0%
Screen Reader: no
Process Argv: /usr/share/code/code --unity-launch

CPU %	Mem MB	PID	Process
9	112	11324	code main
0	16	11328	zygote
16	239	11369	window (● Untitled-22 - Visual Studio Code)
11	80	11443	extensionHost
100	160	11472	electron_node electronForkStart.js tsserver.js
2	48	11476	electron_node typingsInstaller.js tsserver.js typesMap.js
4	80	11376	shared-process
2	64	11359	gpu-process

VS Code version: Code 1.22.1 (950b8b0d37a9b7061b6f0d291837ccc4015f5ecd, 2018-04-06T00:24:49.616Z)
OS version: Linux x64 4.13.0-38-generic

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (4 x 3500)
Load (avg)	2, 2, 1
Memory (System)	15.58GB (0.83GB free)
Process Argv	/usr/share/code/code --disable-extensions
Screen Reader	no
VM	0%

Extensions disabled

Copied from original issue: microsoft/vscode#47717

[mjbvz]

From PJ Carly (@pjcarly) on April 12, 2018 14:10

I've been getting unusual high CPU readings as well since upgrading to 1.22 (from 1.21), used to be a lot lower, now I see per instance of vscode running between 25% and 35% CPU usage (on very decent core i7). On Ubuntu 17.10

This is the output from code --status

Gtk-Message: Failed to load module "pantheon-filechooser-module"

Version: Code 1.22.1 (950b8b0d37a9b7061b6f0d291837ccc4015f5ecd, 2018-04-06T00:24:49.616Z)
OS Version: Linux x64 4.13.0-041300-generic
CPUs: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (4 x 2900)
Memory (System): 7.68GB (0.13GB free)
Load (avg): 5, 5, 4
VM: 0%
Screen Reader: no
Process Argv: /usr/share/code/code --unity-launch

CPU % Mem MB PID Process
 2 47 2410 code main
 0 0 2414 zygote
 3 134 2456 window (targets.js (Working Tree) - myproject - Visual Studio Code)
 0 24 2641 extensionHost
 0 0 4890 electron_node cssServerMain.js
 0 0 4933 electron_node htmlServerMain.js
 53 802 5808 electron_node electronForkStart.js tsserver.js
 0 39 5811 electron_node typingsInstaller.js tsserver.js typesMap.js
 0 0 21200 electron_node jsonServerMain.js
 0 0 2645 terminal
 0 0 2662 /bin/zsh
 0 0 5973 bash /usr/bin/code --status
 21 47 5979 electron_node cli.js
 0 79 5986 /usr/share/code/code --status
 0 24 5988 zygote
 0 31 6019 gpu-process
 0 0 6026 /bin/sh -c /bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
 0 0 6027 /bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
 0 0 5508 searchService
 96 2075 21690 watcherService
 0 24 2467 shared-process
 3 63 2820 window (myproject2 - Visual Studio Code)
 0 0 2843 extensionHost
 0 0 16380 electron_node cssServerMain.js
 0 0 2846 watcherService
 0 0 2847 terminal
 0 0 2871 /bin/zsh
 1 0 16367 gulp
 0 0 8919 searchService
 1 24 21902 window (myproject3 - Visual Studio Code)
 0 0 21929 extensionHost
 0 0 22237 electron_node jsonServerMain.js
 8 16 21930 watcherService
 0 0 21931 terminal
 0 0 21950 /bin/zsh
 2 79 2446 gpu-process

Workspace Stats:
| Window (myproject - Visual Studio Code)
| Folder (myproject): more than 20000 files
| File types: svg(9037) js(7991) less(811) hbs(432) scss(216) json(209)
| md(174) css(174) png(166) woff(91)
| Conf files: package.json(44) grunt.js(26) gulp.js(4) launch.json(1)
| jsconfig.json(1)
| Launch Configs: chrome
| Window (myproject2 - Visual Studio Code)
| Folder (myproject2): more than 20000 files
| File types: php(10861) yml(3111) json(2048) js(686) md(383) test(280)
| scss(279) html(237) png(211) txt(176)
| Conf files: makefile(3) launch.json(2) package.json(2) gulp.js(1)
| jsconfig.json(1)
| Launch Configs: php(2)
| Window (myproject3 - Visual Studio Code)
| Folder (myproject3): more than 20000 files
| File types: js(16819) hbs(970) png(351) css(256) md(250) json(229)
| scss(214) less(198) map(166) svg(81)
| Conf files: package.json(40) grunt.js(11) jsconfig.json(1)

[mjbvz]

Cristian Flores (@critical) In the latest vscode insiders, can you please try collecting the tsserver logs to help us investigate this issue:

1. In VS Code: "typescript.tsserver.log": "verbose"
2. Restart vscode and reproduce the issue
3. In VS Code, run the TypeScript: Open TS Server log command
   1 This should open a folder with a tsserver.log file in it. That is the typings installer log

If you can share that log file, I or someone on the TS team can try looking through them to see what is going on

⚠️Warning: The TypeScript log may include information from your workspace, including file paths and source code names. If you have any concerns about posting this publicly on Github, just let me know and we can arrange something else. On our side, we only use these logs to investigate issues like this

[calinmarina]

I have the same issue on freshly installed vscode version...
I enabled "typescript.tsserver.log": "verbose" and attached the logs here: logs.tar.gz

It's apparently very easy to reproduce:
Step 1. Start VS Code
Step 2. Go to Help > Interactive Playground
Step 3. Try any of the snippets, I've reliably managed to get it to 100%+ CPU each time with: Hovering on if in Refactoring via Extraction section

Here's --status before step 2:

[calin@myThinkPad-T460s:~/.config/Code/logs] (00:53:53)
$code --status

Version: Code 1.22.2 (3aeede733d9a3098f7b4bdc1f66b63b0f48c1ef9, 2018-04-12T16:34:44.222Z)
OS Version: Linux x64 4.13.0-38-generic
CPUs: Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz (4 x 3117)
Memory (System): 19.34GB (3.81GB free)
Load (avg): 1, 1, 1
VM: 0%
Screen Reader: no
Process Argv: /usr/share/code/code --unity-launch

CPU %	Mem MB	 PID	Process
 7	 99	 23021	code main
 0	 20	 23023	 zygote
 15	 257	 23064	 window (settings.json - Visual Studio Code)
 8	 59	 23130	 extensionHost
 4	 59	 23150	 electron_node jsonServerMain.js 
 3	 99	 23069	 shared-process
 3	 79	 23054	 gpu-process

... and after step 3:

[calin@myThinkPad-T460s:~/.config/Code/logs] (00:54:17)
$code --status

Version: Code 1.22.2 (3aeede733d9a3098f7b4bdc1f66b63b0f48c1ef9, 2018-04-12T16:34:44.222Z)
OS Version: Linux x64 4.13.0-38-generic
CPUs: Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz (4 x 3248)
Memory (System): 19.34GB (3.36GB free)
Load (avg): 5, 2, 1
VM: 0%
Screen Reader: no
Process Argv: /usr/share/code/code --unity-launch

CPU %	Mem MB	 PID	Process
 5	 99	 23021	code main
 0	 20	 23023	 zygote
 12	 218	 23064	 window (Interactive Playground - Visual Studio Code)
 5	 79	 23130	 extensionHost
 2	 59	 23150	 electron_node jsonServerMain.js 
 3	 40	 23254	 electron_node cssServerMain.js 
 7	 59	 23255	 electron_node htmlServerMain.js 
 100	 337	 23256	 electron_node electronForkStart.js tsserver.js 
 2	 40	 23272	 electron_node typingsInstaller.js tsserver.js typesMap.js 
 2	 99	 23069	 shared-process
 3	 178	 23054	 gpu-process

OS details:

[calin@myThinkPad-T460s:~/.config/Code] (00:59:54)
$lsb_release -a
LSB Version:	core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
Distributor ID:	Ubuntu
Description:	Ubuntu 17.10
Release:	17.10
Codename:	artful

[mhegazy]

Calin Marina (@calinmarina) can you give typescript@next a try? we have made a few fixes recently hat might impact this scenario.

Please see Using Newer TypeScript Versions documentation for more details on updating your VSCode to use a different version of TypeScript.