Vscode-remote-release: WSL1: High CPU with Ubuntu 20.04

Created on 19 Jun 2020  路  3Comments  路  Source: microsoft/vscode-remote-release

Issue Type: Performance Issue

When I use vs code using WSL remote connection there has been noticeable performance drop and "Not Responding" alert. To see which process is using high CPU it was "node". Please try to rectify this issue as soon as you can.

VS Code version: Code 1.46.1 (cd9ea6488829f560dc949a8b2fb789f3cdc05f5d, 2020-06-17T21:13:20.174Z)
OS version: Windows_NT x64 10.0.19041
Remote OS version: Linux x64 4.4.0-19041-Microsoft


System Info

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-9300H CPU @ 2.40GHz (8 x 2400)|
|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: enabled
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: enabled
webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|7.88GB (3.07GB free)|
|Process Argv||
|Screen Reader|yes|
|VM|50%|

|Item|Value|
|---|---|
|Remote|WSL: Ubuntu-20.04|
|OS|Linux x64 4.4.0-19041-Microsoft|
|CPUs|Intel(R) Core(TM) i5-9300H CPU @ 2.40GHz (8 x 2400)|
|Memory (System)|7.88GB (3.07GB free)|
|VM|50%|


Process Info

CPU %   Mem MB     PID  Process
    1      110    4740  code main
    0      202    2072     window (hello.html - Development [WSL: Ubuntu-20.04] - Visual Studio Code)
    0       83    4516       extensionHost
    0       67   16076         electron_node wslDaemon.js 
    0        6   18208           C:\WINDOWS\System32\wsl.exe -d Ubuntu-20.04 sh -c '"$VSCODE_WSL_EXT_LOCATION/scripts/wslServer.sh" cd9ea6488829f560dc949a8b2fb789f3cdc05f5d stable .vscode-server 5000  '
    0        6    9664             C:\WINDOWS\system32\lxss\wslhost.exe {b1716640-2068-4d68-a1e5-f34c57722979} 468 476 480
    0       13    5984               console-window-host (Windows internal process)
    0       11   10276             console-window-host (Windows internal process)
    0       64    3136     utility
    1      283    7140     gpu-process
    0       57   11016     electron-crash-reporter
    1       93   15888     window (Issue Reporter)
    0       93   15952     shared-process
Fetching remote diagnostics for 'WSL: Ubuntu-20.04' failed: sleep: cannot read realtime clock: Invalid argument



Remote Linux Process info
arunselvanas@ArunselvanAS:~$ ps -aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 8936 312 ? Ssl 22:57 0:00 /init
root 107 0.0 0.0 8940 224 tty2 Ss 23:01 0:00 /init
arunsel+ 108 0.0 0.0 18220 3804 tty2 S 23:01 0:00 -bash
root 138 0.0 0.0 8944 228 tty1 Ss 23:03 0:00 /init
arunsel+ 139 0.0 0.0 10656 688 tty1 S 23:03 0:00 sh -c "$VSCODE_WSL_EXT_LOCATION/scripts/wslServer.s
arunsel+ 140 0.0 0.0 10656 748 tty1 S 23:03 0:00 sh /mnt/c/Users/aruns/.vscode/extensions/ms-vscode-
arunsel+ 162 0.0 0.0 10656 720 tty1 S 23:04 0:00 sh /home/arunselvanas/.vscode-server/bin/cd9ea64888
arunsel+ 164 0.1 0.5 955672 43024 tty1 Sl 23:04 0:01 /home/arunselvanas/.vscode-server/bin/cd9ea6488829f
arunsel+ 198 0.0 0.2 861100 21568 tty1 Sl 23:04 0:01 /home/arunselvanas/.vscode-server/bin/cd9ea6488829f
arunsel+ 205 99.9 0.6 1026760 55420 tty1 Sl 23:04 20:41 /home/arunselvanas/.vscode-server/bin/cd9ea6488829f
arunsel+ 222 0.0 0.0 18052 3508 pts/0 Ss 23:04 0:00 /bin/bash
arunsel+ 232 0.2 1.3 658548 111556 tty1 Sl 23:04 0:02 /home/arunselvanas/.vscode-server/bin/cd9ea6488829f
arunsel+ 298 0.0 0.0 18880 2040 tty2 R 23:24 0:00 ps -


Workspace Info


Fetching remote diagnostics for 'WSL: Ubuntu-20.04' failed: sleep: cannot read realtime clock: Invalid argument
;


Extensions (1)

Extension|Author (truncated)|Version
---|---|---
remote-wsl|ms-|0.44.3


bug performance upstream wsl

Most helpful comment

This is likely because of 'sleep' being broken on WSL1. https://github.com/microsoft/WSL/issues/4898

More discussion relating to VSCode here https://github.com/microsoft/vscode/issues/97568

All 3 comments

I have the same issue with WSL 1.

This is likely because of 'sleep' being broken on WSL1. https://github.com/microsoft/WSL/issues/4898

More discussion relating to VSCode here https://github.com/microsoft/vscode/issues/97568

Yes, looks like a dup of microsoft/WSL#4898. WSL1 and Ubuntu 20.04

@Arunselvan-AS Can you try with a Ubuntu-18.04 distro?

Was this page helpful?
0 / 5 - 0 ratings