-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed
Labels
duplicateexternalfixedCheck the Milestone for the release in which the fix is or will be available.Check the Milestone for the release in which the fix is or will be available.
Milestone
Description
Not sure if it is "C/C++ 0.20.1" issue or "vs code" issue, but this issue only happens when i have "c/c++ 0.20.1" enabled
When using VS Code (ver 1.29.0) with C/C++ (ver 0.20.1), during working with project (changing files, saving files), number of powershell (i am not using it! only editing files) processes increases about 1 per 1~5 minutes (depends on user usage). Number of this processes is not bounded and after couple of hours RAM in my PC depleted (around 100 powershell processes, each using 30MB of RAM)
C:\Users\BoskiDialer>ver
Microsoft Windows [Wersja 6.1.7601]
-> Windows 7 Pro
C:\Users\BoskiDialer>code --status
Version: Code 1.29.0 (5f24c93878bd4bc645a4a17c620e2487b11005f9, 2018-11
-12T07:47:15.448Z)
OS Version: Windows_NT x64 6.1.7601
CPUs: Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz (4 x 2793)
Memory (System): 7.92GB (3.48GB free)
VM: 0%
Screen Reader: no
Process Argv:
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: unavailable_software
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
CPU % Mem MB PID Process
0 87 3744 code main
0 85 1788 shared-process
0 145 2180 gpu-process
0 186 7472 window ([REDACTED] - [REDACTED] - Visual Studio Cod
e)
0 63 3024 extensionHost
0 56 1564 C:/windows/system32/windowspowershell/v1.0/powers
hell.exe -Command [System.Security.Principal.WindowsIdentity]::GetCurrent().Name
0 57 5396 C:/windows/system32/windowspowershell/v1.0/powers
hell.exe -Command [System.Security.Principal.WindowsIdentity]::GetCurrent().Name
0 56 5720 C:/windows/system32/windowspowershell/v1.0/powers
hell.exe -Command [System.Security.Principal.WindowsIdentity]::GetCurrent().Name
0 30 6000 c:\Users\BoskiDialer\.vscode\extensions\ms-vscode
.cpptools-0.20.1\bin\Microsoft.VSCode.CPP.Extension.exe
0 9 920 c:\Users\BoskiDialer\.vscode\extensions\ms-vsco
de.cpptools-0.20.1/bin/Microsoft.VSCode.CPP.IntelliSense.Msvc.exe 6000 0
0 10 8076 c:\Users\BoskiDialer\.vscode\extensions\ms-vsco
de.cpptools-0.20.1/bin/Microsoft.VSCode.CPP.IntelliSense.Msvc.exe 6000 1
0 56 6616 C:/windows/system32/windowspowershell/v1.0/powers
hell.exe -Command [System.Security.Principal.WindowsIdentity]::GetCurrent().Name
0 56 6808 C:/windows/system32/windowspowershell/v1.0/powers
hell.exe -Command [System.Security.Principal.WindowsIdentity]::GetCurrent().Name
0 56 7224 C:/windows/system32/windowspowershell/v1.0/powers
hell.exe -Command [System.Security.Principal.WindowsIdentity]::GetCurrent().Name
0 56 7800 C:/windows/system32/windowspowershell/v1.0/powers
hell.exe -Command [System.Security.Principal.WindowsIdentity]::GetCurrent().Name
0 56 8140 C:/windows/system32/windowspowershell/v1.0/powers
hell.exe -Command [System.Security.Principal.WindowsIdentity]::GetCurrent().Name
0 57 8500 C:/windows/system32/windowspowershell/v1.0/powers
hell.exe -Command [System.Security.Principal.WindowsIdentity]::GetCurrent().Name
0 56 8748 C:/windows/system32/windowspowershell/v1.0/powers
hell.exe -Command [System.Security.Principal.WindowsIdentity]::GetCurrent().Name
0 57 8812 C:/windows/system32/windowspowershell/v1.0/powers
hell.exe -Command [System.Security.Principal.WindowsIdentity]::GetCurrent().Name
0 11 8208 watcherService
Workspace Stats:
| Window ([REDACTED] - [REDACTED] - Visual Studio Code)
| Folder ([REDACTED]): 1518 files
| File types: o(425) su(405) h(205) c(123) d(45) obj(44) prefs(37)
| json(18) exe(17) mk(16)
| Conf files: settings.json(9) makefile(7)
I am not sure if this is related to Window Title bar issue, but i have both this issues at the same time.
Metadata
Metadata
Assignees
Labels
duplicateexternalfixedCheck the Milestone for the release in which the fix is or will be available.Check the Milestone for the release in which the fix is or will be available.