vscode: Crashes every day with "Code: '5'"
Issue Type: Performance Issue
My VSCode instance crashes every day. I have switched recently, so I cannot state since when exactly. I cannot bind these chrases to any specific set of reproducible actions — it looks just random.
I can somewhat predict it’s going to crash soon because it starts to respond sluggishly seconds or a couple of minutes before a crash. For example, switching to a different tab takes ~2-5 seconds to complete when this happens. That usually signals it’s about to crash soon.
The crash dialog doesn’t provide any meaningful information, just a laconic, cryptic reason: 'crashed', code: '5' line.
VS Code version: Code 1.64.2 (f80445acd5a3dadef24aa209168452a3d97cc326, 2022-02-09T22:00:58.347Z) OS version: Darwin x64 21.2.0 Restricted Mode: No
System Info
| Item | Value |
|---|---|
| CPUs | Intel® Core™ i5-8259U CPU @ 2.30GHz (8 x 2300) |
| GPU Status | 2d_canvas: enabled gpu_compositing: enabled metal: disabled_off multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled skia_renderer: disabled_off_ok video_decode: enabled webgl: enabled webgl2: enabled |
| Load (avg) | 4, 4, 4 |
| Memory (System) | 8.00GB (1.02GB free) |
| Process Argv | –crash-reporter-id 1004a7b4-dd6b-4c5b-97a9-c41af381dd3c |
| Screen Reader | no |
| VM | 0% |
Process Info
CPU % Mem MB PID Process
17 90 39780 code main
0 33 39783 gpu-process
0 8 39785 utility-network-service
0 49 40144 shared-process
0 25 40160 ptyHost
0 0 40457 node /Users/jaime/.nvm/versions/node/v17.2.0/bin/yarn run start:web
0 0 40477 /Users/jaime/.nvm/versions/node/v17.2.0/bin/node --require /Users/jaime/.nvm/versions/node/v17.2.0/lib/node_modules/corepack/dist/vcc.js /Users/jaime/.node/corepack/yarn/3.1.1/yarn.js run start:web
0 0 40553 /Users/jaime/.nvm/versions/node/v17.2.0/bin/node /Users/jaime/.nvm/versions/node/v17.2.0/lib/node_modules/corepack/dist/yarn.js workspace @c20/web dev
0 0 40554 /Users/jaime/.nvm/versions/node/v17.2.0/bin/node --require /Users/jaime/.nvm/versions/node/v17.2.0/lib/node_modules/corepack/dist/vcc.js /Users/jaime/.node/corepack/yarn/3.1.1/yarn.js workspace @c20/web dev
0 0 40566 /Users/jaime/.nvm/versions/node/v17.2.0/bin/node /Users/jaime/Code/c20/.yarn/releases/yarn-3.1.1.cjs workspace @c20/web dev
0 8 40570 /Users/jaime/.nvm/versions/node/v17.2.0/bin/node /Users/jaime/Code/c20/node_modules/next/dist/bin/next dev
0 0 40580 node /Users/jaime/.nvm/versions/node/v17.2.0/bin/yarn run start:api
0 0 40582 /Users/jaime/.nvm/versions/node/v17.2.0/bin/node --require /Users/jaime/.nvm/versions/node/v17.2.0/lib/node_modules/corepack/dist/vcc.js /Users/jaime/.node/corepack/yarn/3.1.1/yarn.js run start:api
0 0 40589 /Users/jaime/.nvm/versions/node/v17.2.0/bin/node /Users/jaime/.nvm/versions/node/v17.2.0/lib/node_modules/corepack/dist/yarn.js workspace @c20/api start
0 0 40590 /Users/jaime/.nvm/versions/node/v17.2.0/bin/node --require /Users/jaime/.nvm/versions/node/v17.2.0/lib/node_modules/corepack/dist/vcc.js /Users/jaime/.node/corepack/yarn/3.1.1/yarn.js workspace @c20/api start
0 0 40597 /Users/jaime/.nvm/versions/node/v17.2.0/bin/node /Users/jaime/Code/c20/.yarn/releases/yarn-3.1.1.cjs workspace @c20/api start
0 0 40601 /Users/jaime/.nvm/versions/node/v17.2.0/bin/node /Users/jaime/Code/c20/node_modules/nodemon/bin/nodemon.js src/server.ts
0 8 47554 /Users/jaime/.nvm/versions/node/v17.2.0/bin/node /Users/jaime/Code/c20/node_modules/ts-node/dist/bin.js src/server.ts
0 25 62305 node /Users/jaime/.nvm/versions/node/v17.2.0/bin/yarn run start:api
0 82 62308 /Users/jaime/.nvm/versions/node/v17.2.0/bin/node --require /Users/jaime/.nvm/versions/node/v17.2.0/lib/node_modules/corepack/dist/vcc.js /Users/jaime/.node/corepack/yarn/3.1.1/yarn.js run start:api
0 25 62314 /Users/jaime/.nvm/versions/node/v17.2.0/bin/node /Users/jaime/.nvm/versions/node/v17.2.0/lib/node_modules/corepack/dist/yarn.js workspace @c20/api start
0 25 62317 /Users/jaime/.nvm/versions/node/v17.2.0/bin/node --require /Users/jaime/.nvm/versions/node/v17.2.0/lib/node_modules/corepack/dist/vcc.js /Users/jaime/.node/corepack/yarn/3.1.1/yarn.js workspace @c20/api start
0 82 62320 /Users/jaime/.nvm/versions/node/v17.2.0/bin/node /Users/jaime/Code/c20/.yarn/releases/yarn-3.1.1.cjs workspace @c20/api start
0 33 62324 /Users/jaime/.nvm/versions/node/v17.2.0/bin/node /Users/jaime/Code/c20/node_modules/nodemon/bin/nodemon.js src/server.ts
0 25 62260 fileWatcher
0 0 62374 /bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
0 156 62254 window (company.ts — c20)
0 49 62257 extensionHost
0 25 62264 /Applications/Visual Studio Code.app/Contents/MacOS/Electron --ms-enable-electron-run-as-node --max-old-space-size=3072 /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js --serverMode partialSemantic --useInferredProjectPerProjectRoot --disableAutomaticTypingAcquisition --cancellationPipeName /var/folders/jf/y8xgq9yd6yv3bn0wr2mwpxhw0000gn/T/vscode-typescript501/351cc628b6420b13b793/tscancellation-a155a17769e33a7e0c8d.tmp* --locale en --noGetErrOnBackgroundUpdate --validateDefaultNpmLocation
1 33 62265 /Applications/Visual Studio Code.app/Contents/MacOS/Electron --ms-enable-electron-run-as-node --max-old-space-size=3072 /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js --useInferredProjectPerProjectRoot --enableTelemetry --cancellationPipeName /var/folders/jf/y8xgq9yd6yv3bn0wr2mwpxhw0000gn/T/vscode-typescript501/351cc628b6420b13b793/tscancellation-0dc703249f57b491be5d.tmp* --locale en --noGetErrOnBackgroundUpdate --validateDefaultNpmLocation
0 33 62268 /Applications/Visual Studio Code.app/Contents/MacOS/Electron --ms-enable-electron-run-as-node /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/typingsInstaller.js --globalTypingsCacheLocation /Users/jaime/Library/Caches/typescript/4.5 --enableTelemetry --typesMapLocation /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/typesMap.json --validateDefaultNpmLocation
0 49 62286 /Applications/Visual Studio Code.app/Contents/MacOS/Electron --ms-enable-electron-run-as-node /Users/jaime/.vscode/extensions/dbaeumer.vscode-eslint-2.2.2/server/out/eslintServer.js --node-ipc --clientProcessId=62257
0 33 62302 /Applications/Visual Studio Code.app/Contents/MacOS/Electron --ms-enable-electron-run-as-node /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/json-language-features/server/dist/node/jsonServerMain --node-ipc --clientProcessId=62257
1 66 62369 issue-reporter
Workspace Info
| Window (company.ts — c20)
| Folder (c20): 10757 files
| File types: gz(6678) zip(2595) js(519) json(213) ts(105) mdx(92)
| pack(44) map(40) html(29) md(25)
| Conf files: package.json(6) tsconfig.json(5) github-actions(2)
| settings.json(1) tasks.json(1);
Extensions (17)
| Extension | Author (truncated) | Version |
|---|---|---|
| better-comments | aar | 2.1.0 |
| unique-lines | bib | 1.0.0 |
| vscode-eslint | dba | 2.2.2 |
| xml | Dot | 2.5.1 |
| vscode-html-css | ecm | 1.11.0 |
| EditorConfig | Edi | 0.16.4 |
| prettier-vscode | esb | 9.2.0 |
| vscode-pull-request-github | Git | 0.36.1 |
| customize-ui | ioc | 0.1.58 |
| monkey-patch | ioc | 0.1.16 |
| rainbow-csv | mec | 2.0.0 |
| dotenv | mik | 1.0.1 |
| vscode-language-pack-es | MS- | 1.64.6 |
| remote-containers | ms- | 0.217.4 |
| emoji | Per | 1.0.1 |
| vscode-sort-json | ric | 1.20.0 |
| vscode-sort-package-json | uni | 1.2.2 |
(2 theme extensions excluded)
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 7
- Comments: 21 (3 by maintainers)
I started seeing crashes as well (crashed, code 5), a few days ago (?)- I’m not sure if something has changed in the VS or in my dev environment. It happens extremely frequently, esp. when working with unit tests and assessing failed cases (when the peek dialog is displayed) - VS Code crashes every couple of minutes 😕
It’s really easy to reproduce, so if anyone is willing, I can grab some logs, but I need instructions.
FWIW, I’m on MacOS 11/Big Sur
Thank you, John. Seems like a good starting point. I have just disabled all the 13 non-essential extensions I have installed. I will slowly re-enable them during the following days. That may provide insight. For the record, I jot down here the essential four I am starting with.
Extensions (4)