vscode: High CPU Usage on Windows with Mapped Drive when leaving VS Code Open for a while

Issue Type: Performance Issue

Open a large folder from a mapped drive in VS Code
Work in VS Code for a while, or just leave it open

Expected Outcome CPU might spike during use, but should drop back down

Actual Outcome CPU spikes and stays up in the double digits, often as high as 60-80%, causing the editor and other apps on the machine to be almost unusable.

VS Code version: Code 1.32.3 (a3db5be9b5c6ba46bb7555ec5d60178ecc2eaae4, 2019-03-14T23:43:35.476Z) OS version: Windows_NT x64 10.0.17134

System Info

Item	Value
CPUs	Intel® Core™ i5-5200U CPU @ 2.20GHz (4 x 2195)
GPU Status	2d_canvas: enabled checker_imaging: disabled_off 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: enabled surface_synchronization: enabled_on video_decode: enabled webgl: enabled webgl2: enabled
Memory (System)	7.91GB (0.77GB free)
Process Argv
Screen Reader	no
VM	0%

Process Info

CPU %	Mem MB	   PID	Process
   16	    76	 10668	code main
    0	    60	  5324	   shared-process
   31	   299	  8124	   window (Picker.js - Visual Studio Code)
    0	    31	  5488	     searchService
    0	    11	 11840	     electron-crash-reporter
    0	   152	 18992	     extensionHost
    0	    25	  5984	       "C:\Program Files\Microsoft VS Code\Code.exe" "c:\Program Files\Microsoft VS Code\resources\app\extensions\html-language-features\server\dist\htmlServerMain" --node-ipc --clientProcessId=18992
   23	   352	  8808	       electron_node tsserver.js 
    0	    58	 11072	       electron_node eslintServer.js 
    0	    14	 22128	     watcherService 
    0	     5	 13004	       console-window-host (Windows internal process)
    1	    67	 13880	   window (Issue Reporter)
    1	   479	 14708	   gpu-process

Workspace Info

|  Window (Picker.js - Visual Studio Code)
|    Folder (Acadia): 12555 files
|      File types: html(5570) js(3688) map(1134) java(515) png(448) cfm(259)
|                  less(185) htm(161) cfc(102) snap(100)
|      Conf files: package.json(2) gulp.js(1) webpack.config.js(1)
|                  launch.json(1) settings.json(1)
|      Launch Configs: node(2);

Extensions (19)

Extension	Author (truncated)	Version
vscode-nsp	ada	1.0.1
vscode-eslint	dba	1.8.2
xml	Dot	2.4.0
coldfusion	ili	1.0.1
backbone-js-snippets	ioa	0.0.1
docthis	joe	0.7.1
prettify-json	moh	0.0.3
mssql	ms-	1.4.0
sublime-keybindings	ms-	4.0.0
debugger-for-chrome	msj	4.11.3
java	red	0.40.0
vscode-sort-json	ric	1.13.0
vscodeintellicode	Vis	1.1.4
vscode-java-debug	vsc	0.17.0
vscode-java-dependency	vsc	0.3.0
vscode-java-pack	vsc	0.6.0
vscode-java-test	vsc	0.15.0
vscode-maven	vsc	0.15.1
cordova-tools	vsm	1.8.0

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 2
Comments: 23 (12 by maintainers)

Most upvoted comments

Bumping this discussion to indicate this probably requires a fix to Electron’s node to address the Cannot read property 'close' of undefined issue https://github.com/electron/node/pull/97

shiftkey on Mar 22, 2019

First I’ve hit it is on 1.32.x (i think 1.32.0, but maybe 1.32.1). I’ll read through the tips, and keep an eye on process explorer. Will update, but might not be until Monday as I’m getting ready to wrap up for the day and haven’t tried to repro on my home computer

rdwoodring on Mar 15, 2019