Today (2023-04-03) VS Code is crashing whenever a Python file is opened in the mixed language repository https://gitlab.cern.ch/gstark/pycolumnarprototype
This behavior has not been observed until today. The machine uptime has been minimal.
$ uptime
17:57:25 up 14:11, 1 user, load average: 2.04, 2.15, 2.04If a Python file is opened with VS Code after about 3-5 seconds VS Code will freeze and then crash with the following error message.
The window terminated unexpectedly (reason:'crashed', code:'133')
See error-window-code-133.png for a screenshot.
Version: 1.77.0
Commit: 7f329fe6c66b0f86ae1574c2911b681ad5a45d63
Date: 2023-03-29T10:05:35.165Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: 10.2.154.26-electron.0
OS: Linux x64 5.19.0-38-generic
Sandboxed: No
$ grep -r 'code: 133' ~/.config/Code/logs
/home/feickert/.config/Code/logs/20230403T170651/main.log:2023-04-03 17:23:40.755 [error] CodeWindow: renderer process gone (reason: crashed, code: 133)
/home/feickert/.config/Code/logs/20230403T173249/main.log:2023-04-03 17:33:17.753 [error] CodeWindow: renderer process gone (reason: crashed, code: 133)
/home/feickert/.config/Code/logs/20230403T164429/main.log:2023-04-03 16:46:09.761 [error] CodeWindow: renderer process gone (reason: crashed, code: 133)Contents of the attached main.log
$ cat /home/feickert/.config/Code/logs/20230403T173249/main.log
2023-04-03 17:32:49.870 [info] [SharedProcess] using utility process
2023-04-03 17:32:49.929 [info] update#setState idle
2023-04-03 17:32:53.879 [info] [UtilityProcess type: shared-process, pid: <none>]: creating new...
2023-04-03 17:32:53.884 [info] [UtilityProcess type: shared-process, pid: 213637]: successfully created
2023-04-03 17:32:54.165 [info] [UtilityProcess id: 1, type: fileWatcher, pid: <none>]: creating new...
2023-04-03 17:32:54.170 [info] [UtilityProcess id: 1, type: fileWatcher, pid: 213677]: successfully created
2023-04-03 17:32:54.239 [info] [UtilityProcess id: 1, type: extensionHost, pid: <none>]: creating new...
2023-04-03 17:32:54.245 [info] [UtilityProcess id: 1, type: extensionHost, pid: 213695]: successfully created
2023-04-03 17:33:17.753 [error] CodeWindow: renderer process gone (reason: crashed, code: 133)
2023-04-03 17:33:19.292 [info] [UtilityProcess id: 1, type: fileWatcher, pid: 213677]: received exit event with code 0
2023-04-03 17:33:19.388 [error] [UtilityProcess id: 1, type: fileWatcher, pid: 213677]: crashed with code 139 and reason 'crashed'
2023-04-03 17:33:19.930 [info] update#setState checking for updates
2023-04-03 17:33:19.997 [info] update#setState idle
2023-04-03 17:33:20.927 [info] [UtilityProcess id: 1, type: extensionHost, pid: 213695]: waiting to exit...
2023-04-03 17:33:23.134 [info] [UtilityProcess id: 1, type: extensionHost, pid: 213695]: received exit event with code 0
2023-04-03 17:33:23.134 [info] Extension host with pid 213695 exited with code: 0, signal: unknown.Given Anthony Shaw's input it was noticed that the problem was not replicable if VS Code was started with code --disable-extensions. Though if all the extensions were enabled the following window1/renderer.log was found before crash
2023-04-03 22:38:22.249 [warning] Via 'product.json#extensionEnabledApiProposals' extension 'ms-vscode.vscode-selfhost-test-provider' wants API proposal 'testContinuousRun' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
2023-04-03 22:38:22.259 [warning] Via 'product.json#extensionEnabledApiProposals' extension 'ms-vscode.remote-repositories' wants API proposal 'contribEditorGutterMenu' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
2023-04-03 22:38:22.259 [warning] Via 'product.json#extensionEnabledApiProposals' extension 'github.vscode-pull-request-github' wants API proposal 'contribEditorGutterMenu' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
2023-04-03 22:38:22.259 [warning] Via 'product.json#extensionEnabledApiProposals' extension 'ms-toolsai.jupyter' wants API proposal 'notebookControllerKind' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
2023-04-03 22:38:23.459 [error] [Extension Host] (node:41758) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `exe --trace-deprecation ...` to show where the warning was created)
2023-04-03 22:38:25.220 [info] [perf] Render performance baseline is 31ms
I'm not sure what to do about the
(Use `exe --trace-deprecation ...` to show where the warning was created)
part though given that
$ code --trace-deprecation
Warning: 'trace-deprecation' is not in the list of known options, but still passed to Electron/Chromium.The DeprecationWarning: Buffer() extension hasn't been identified yet, but the offending extension that is causing the crash is the v2023.3.1000892223 (2023-03-28) release of the official Jupyter extension from Microsoft. It is actually the Jupyter extension and not the 4 extensions it packages as those can all be turned back on after the Jupyter extension is disabled and there are no errors.
The extension causing the DeprecationWarning: Buffer() warning is the official Microsoft Live Share extension v1.0.5834.
c.f. https://github.com/microsoft/vscode-jupyter/issues/13264
- Restarting VS Code
- Restarting VS Code without "Don't restore editors" option checked
- Opening Python files in other projects with no crash and then opening a Python file in the offending project
- Cloning the project fresh under /tmp and trying to open a Python file in the new repository
- Power cycling machine
