import-cost: Memory leak

From @maxibanki on October 31, 2017 0:13

  • VSCode Version: Code - Insiders 1.18.0-insider (8deed535e26bc8ceebf83a9aa631580ebd610918, 2017-10-30T05:21:47.015Z)
  • OS Version: Windows_NT x64 6.1.7601
  • Extensions:
Extension Author (truncated) Version
markdown-checkbox bie 0.0.3
jshint dba 0.10.15
vscode-eslint dba 1.4.0
githistory don 0.2.3
xml Dot 1.9.2
gitlens eam 5.7.1
tslint eg2 1.0.14
vscode-abap lar 0.1.0
Go luk 0.6.66
postscript max 1.0.0
code-beautifier mic 1.7.2
debugger-for-chrome msj 3.4.0
vetur oct 0.10.1
vscode-docker Pet 0.0.20
vscode-icons rob 7.17.0
vscode-table-formatter shu 1.2.1
vscode-hexdump sle 1.6.0
addDocComments ste 0.0.8
html-preview-vscode tht 0.1.1
vscode-import-cost wix 2.5.1

(1 theme extensions excluded)


Steps to Reproduce: (not reproduceable)

  1. Open Vetur settings
  2. Click on contributions

Reproduces without extensions: Yes/No

Processes: procexp64_2017-10-31_00-36-29 Command line: "C:\Programme\VSCodeInsider\Code - Insiders.exe" C:\Users\mxs\.vscode-insiders\extensions\wix.vscode-import-cost-2.5.1\node_modules\worker-farm\lib\child\index.js "C:\Programme\VSCodeInsider\Code - Insiders.exe" c:\Programme\VSCodeInsider\resources\app\out\bootstrap --type=extensionHost Process Explorer Performance Tab: procexp64_2017-10-31_00-42-11

Hi,

I’m not so familiar with the process structure of VS Code, but in the command line arguments of the process which used so much RAM, there is the extension wix.vscode-import-cost-2.5.1 loading. Could this process used only for this extension, so that this is the cause of the high memory usage?

I tried to run the Dev Tools Performance Profiler, but it never finished, because of the always 100% usage of my memory in my notebook I think.

Best regards

Copied from original issue: Microsoft/vscode#37192

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Reactions: 14
  • Comments: 21 (3 by maintainers)

Most upvoted comments

This is still a BIG problem, i have to give up on this extension.

I really love this plugin but it was using 1.5GB of memory, which I can’t really live with!

Had to remove this plugin because of the memory leak and causing lock ups.

image

This is this extension consuming 10GB of RAM on VSCode WSL Windows 10 1909. I’ll have to give up on it.