Open jazelly opened 1 year ago
I saw this issue on MacOS as well. After running bisect it was determined that this one was causing the issue.
Still happening today.
In a (very) large project, containing lots of ts
files, whenever the entire project is re-built, there are so many rg
processes being spawned that they end-up causing EMFILE
error (ulimit reached).
The following is an extract of my "Extension Host" output that contains thousands more lines like this one:
2024-02-16 15:04:50.619 [error] Error: spawn /Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar.unpacked/@vscode/ripgrep/bin/rg EMFILE
at P (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1884:5882)
at vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1892:4355
at async vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1892:2925
2024-02-16 15:04:50.620 [error] Error: spawn /Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar.unpacked/@vscode/ripgrep/bin/rg EMFILE
at P (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1884:5882)
at vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1892:4355
at async vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1892:2925
Version: Code 1.77.0 (7f329fe6c66b0f86ae1574c2911b681ad5a45d63, 2023-03-29T10:02:16.981Z) OS Version: Windows_NT x64 10.0.19044 CPUs: Intel(R) Core(TM) i5-10500 CPU @ 3.10GHz (12 x 3096) Memory (System): 15.94GB (4.44GB free)
After checking out tags in a large repo, say
node/node.js
, this happened due to large file system update:code --status
crash-status2.txtI can confirm this is not an issue with VSCode, as with a clean run, i.e. no extension, it works fine. I had only this extension enabled.
Currently I have to disable this extension while working on repos like this.