VS Code extension causing crash when Python files are opened

Applies To

[ ] Notebooks (.ipynb files)
[ ] Interactive Window and\/or Cell Scripts (.py files with #%% markers)

What happened?

I had been able to work with Python files normally in VS Code until the afternoon of 2023-04-03 when VS Code started crashing with user error window of "The window terminated unexpectedly (reason:'crashed', code:'133')"

error-window-code-133

and main.log of

$ cat ~.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.

This is for VS Code:

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

I have summarized my debugging experience to arrive at ms-toolsai.jupyter as being the offending extension in the following GitHub Gist: https://gist.github.com/matthewfeickert/8c3698bc5f64effdaf9f345e060c8b41

VS Code Version

1.77.0

Jupyter Extension Version

2023.3.1000892223

Jupyter logs

Visual Studio Code (1.77.0, undefined, desktop)
Jupyter Extension Version: 2023.3.1000892223.
Python Extension Version: 2023.6.0.
Workspace folder /home/feickert/Code/GitHub/pyhf
User belongs to experiment group 'jupyterEnhancedDataViewer'
User belongs to experiment group 'jupyterTestcf'
info 00:27:13.539: LSP Notebooks experiment is enabled
info 00:27:13.821: Process Execution: > ~/.pyenv/versions/3.10.4/envs/base/bin/python -m pip list
> ~/.pyenv/versions/3.10.4/envs/base/bin/python -m pip list

Coding Language and Runtime Version

Python v3.10.4

Language Extension Version (if applicable)

Python Extension Version: 2023.6.0

Anaconda Version (if applicable)

No response

Running Jupyter locally or remotely?

Local

Same problem for me since this morning with two different Ubuntu computers. VS Code and Codium have the same problem. Working fine yesterday.

Version : v2023.3.1000892223

Trying with v2023.4.1000952452 don't solve the problem.

@DonJayamanne can you have a look at this please. Have done some triaging with the user (see linked gist)

@DonJayamanne can you have a look at this please. Have done some triaging with the user (see linked gist)

Thanks for your time that you've already spent on this, @tonybaloney. :pray: It was super appreciated.

Can confirm this issue. However, I'm getting the error code 132.

Same problem for me since this morning with two different Ubuntu computers. VS Code and Codium have the same problem. Working fine yesterday.

Version : v2023.3.1000892223

Trying with v2023.4.1000952452 don't solve the problem.

Sorry, it seems that in my case it is a mistake from me using Plotly graph with tickmode="linear", that create a too big object to be displayed. My apologies

@benoit-cty @HeKR96 @matthewfeickert

Does the extension host crash when you open another workspace folder with a simple notebook or simple python file?
Please could you install the previous version of the Jupyter extension 2023.02.* and let me know if VS Code extension host still crashes?
Next, please could you add the following setting into your user settings file, reload vscode and let me know if VS Code extension still crashes (with the latest version of Jupyter extension)
```
// Ignore any squigglies you get, this is not an officially supported setting, hence the warnings
"jupyter.disableZMQSupport": true
```
Finally, please could you provide your OS info, so I can try to setup the same linux OS at my end to see if I can repro this.

@DonJayamanne

The crashes also occur in a new folder, with one python file and one jupyter notebook file.
v2023.2.1200692131 also crashes for me
Does not change anything. Still crashing.
I'm on openSUSE Leap 15.4 with KDE Plasma 5.24.4 During the tests, I had the following extensions enabled: Python, Jupyter, Jupyter Cell Tags, Jupyter Keymap, Juptyer Notebook Renderers and Jupyter Slide Show

Can you try disabling all extensions except for python and let me know if that makes a difference

Hello, I'm experiencing the same issue since April 5th on Ubuntu 22.04.2 LTS and VSCode 1.77.2. Tried disabling all extensions except for Python but still ran into the same issue unfortunately.

@matthewfeickert @HeKR96 Can you try disabling the Jupyter extension and see if the problem happens?

@karrtikr Does not crash when jupyter is disabled.

@karrtikr Does not crash when jupyter is disabled.

Same for me, and re-enabling freeze VS Code again (The window is not responding).

Same here, too. VSCode crashes reliably, when ms-toolsai.jupyter is enabled. Disabling will prevent the crashes. BTW: can really recommend the extension bisect feature of VSCode, which helpled to track down the extension quickly: https://github.com/microsoft/vscode-docs/blob/vnext/release-notes/v1_52.md#troubleshooting-extension-bisect

Can you try running Developer: toggle developer tools and open the console tab, then opening a .py file to trigger the issue and see if any error logs show up there? Also, open the extension host logs in the output panel to see if any errors show there since this sounds like an error during extension activation.

actually, these instructions would likely provide a helpful crash dump for us https://github.com/microsoft/vscode/wiki/Native-Crash-Issues

Unfortunately, the last output (some significant time before the crash happens) is unrelated, I think:

2023-04-18 09:03:11.742 [info] ExtensionService#_doActivateExtension 42Crunch.vscode-openapi, startup: true, activationEvent: '*'
2023-04-18 09:03:11.872 [info] ExtensionService#_doActivateExtension mermade.openapi-lint, startup: true, activationEvent: '*'
2023-04-18 09:03:12.251 [info] Eager extensions activated
2023-04-18 09:03:12.317 [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: false, activationEvent: 'onStartupFinished'
2023-04-18 09:03:12.319 [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'
2023-04-18 09:03:12.323 [info] ExtensionService#_doActivateExtension amodio.toggle-excluded-files, startup: false, activationEvent: 'onStartupFinished'
2023-04-18 09:03:12.325 [info] ExtensionService#_doActivateExtension dbaeumer.vscode-eslint, startup: false, activationEvent: 'onStartupFinished'
2023-04-18 09:03:12.333 [info] ExtensionService#_doActivateExtension eamodio.gitlens, startup: false, activationEvent: 'onStartupFinished'
2023-04-18 09:03:12.362 [info] ExtensionService#_doActivateExtension vscode.npm, startup: false, activationEvent: 'onStartupFinished', root cause: esbenp.prettier-vscode
2023-04-18 09:03:12.368 [info] ExtensionService#_doActivateExtension streetsidesoftware.code-spell-checker, startup: false, activationEvent: 'onStartupFinished'
2023-04-18 09:03:12.416 [warning] [redhat.vscode-yaml] Accessing a resource scoped configuration without providing a resource is not expected. To get the effective value for '[yaml]', provide the URI of a resource or 'null' for any resource.
2023-04-18 09:03:12.577 [warning] [redhat.vscode-yaml] Accessing a resource scoped configuration without providing a resource is not expected. To get the effective value for '[yaml]', provide the URI of a resource or 'null' for any resource.
2023-04-18 09:03:13.024 [info] ExtensionService#_doActivateExtension esbenp.prettier-vscode, startup: false, activationEvent: 'onStartupFinished'
2023-04-18 09:03:16.171 [error] {"message":"Git relative path not found."}

not sure though.

There's nothing more added to the log, as the GUI completely freezes.

Also I cannot reproduce the crash when starting code with code --crash-reporter-directory <absolute-path>, as in the link you shared. For some strange reasons, code does not crash then. But opening the exact same file in the same repo when not in crash dump mode crashes the GUI. No idea why.

Could you provide the python.log and jupyter.log files if they exist in the directory that gets opened with the Developer: open extension logs folder command? The jupyter.log might be in a outputlogging* subfolder.

Also, it sounded like rolling back the jupyter extension didn't resolve the issue - does rolling back the python extension help?

@hansmannj to clarify did you replace <absolute-path> with a valid path ? The command should be as follows code --crash-reporter-directory /tmp/vscode-extension-crash

@amunger: Thanks a lot for having a look at this! Sure, here's Python.log:

[LIST OF PATHS TO MANY VENVS]
[SNIP]

> /bin/python3 -I ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/interpreterInfo.py
> /bin/python3.5 -I ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/interpreterInfo.py
> /bin/python3.7 -I ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/interpreterInfo.py
> /bin/python3.8 -I ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/interpreterInfo.py
> /bin/python3.9 -I ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/interpreterInfo.py
> /usr/bin/python3 -I ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/interpreterInfo.py
> /usr/bin/python3.5 -I ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/interpreterInfo.py
> /usr/bin/python3.7 -I ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/interpreterInfo.py
> /usr/bin/python3.8 -I ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/interpreterInfo.py
> /usr/bin/python3.9 -I ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/interpreterInfo.py
> /usr/include/python3.5 -I ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/interpreterInfo.py
[ERROR 2023-3-18 21:18:52.392]: Error: Command failed: /usr/include/python3.5 -I /home/USERNAME/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/get_output_via_markers.py /home/USERNAME/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/interpreterInfo.py
/bin/sh: 1: /usr/include/python3.5: Permission denied

    at ChildProcess.exithandler (node:child_process:408:12)
    at ChildProcess.emit (node:events:526:28)
    at ChildProcess.emit (node:domain:475:12)
    at maybeClose (node:internal/child_process:1092:16)
    at Socket.<anonymous> (node:internal/child_process:451:11)
    at Socket.emit (node:events:526:28)
    at Socket.emit (node:domain:475:12)
    at Pipe.<anonymous> (node:net:687:12) {
  killed: false,
  code: 126,
  signal: null,
  cmd: '/usr/include/python3.5 -I /home/USERNAME/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/get_output_via_markers.py /home/USERNAME/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/interpreterInfo.py'
}
> /usr/include/python3.7 -I ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/interpreterInfo.py
[ERROR 2023-3-18 21:18:52.431]: Error: Command failed: /usr/include/python3.7 -I /home/USERNAME/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/get_output_via_markers.py /home/USERNAME/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/interpreterInfo.py
/bin/sh: 1: /usr/include/python3.7: Permission denied

    at ChildProcess.exithandler (node:child_process:408:12)
    at ChildProcess.emit (node:events:526:28)
    at ChildProcess.emit (node:domain:475:12)
    at maybeClose (node:internal/child_process:1092:16)
    at Socket.<anonymous> (node:internal/child_process:451:11)
    at Socket.emit (node:events:526:28)
    at Socket.emit (node:domain:475:12)
    at Pipe.<anonymous> (node:net:687:12) {
  killed: false,
  code: 126,
  signal: null,
  cmd: '/usr/include/python3.7 -I /home/USERNAME/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/get_output_via_markers.py /home/USERNAME/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/interpreterInfo.py'
}

and here Jupyter.log:

Visual Studio Code (1.77.3, undefined, desktop)
Jupyter Extension Version: 2023.3.1201040234.
Python Extension Version: 2023.6.1.
Workspace folder /home/USERNAME/local_dev/REPONAME
User belongs to experiment group 'jupyterEnhancedDataViewer'
User belongs to experiment group 'jupyterTestcf'
info 21:18:43.488: LSP Notebooks experiment is enabled
info 21:19:19.356: Shutting down notebooks for 9bd99c84-948d-4d04-8526-5de4ffddc373
info 21:19:19.356: Disposing HostJupyterExecution 3e1bf3a9-5c92-4ac8-a756-b2173a1f44ee
info 21:19:19.356: Disposing HostJupyterExecution 3e1bf3a9-5c92-4ac8-a756-b2173a1f44ee

Permissions are lrwxrwxrwx for Python3.5 and 3.7 but it's both symlinks, the actual link target folders having drwxr-xr-x

BTW:

code --version                                                        
1.77.3
704ed70d4fd1c6bd6342c436f1ede30d1cff4710
x64

and

lsb_release -a 
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.2 LTS
Release:    22.04
Codename:   jammy

@deepak1556: yes, I was using a valid directory in the command

Did not try any roll backs so far, only disabling the extension, which fixed the issue. I'll try to roll back and see if that helps, tomorrow (it's later evening in my timezone and I had a long day :wink:)

thanks for helping investigate. It's more likely that whatever operation came after those logs caused the crash since the error was caught and logged for 3.5 and 3.7. Is there another interpreter in /usr/include/, and can you check if it's a valid symlink? You could try running that same command for it too:

/usr/include/python* -I ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/interpreterInfo.py

Were you able to check in the Developer tools console as well? An extension host crash should show up in there. Developer: Toggle Developer Tools

Can other users facing the crash also try to get the crash logs following the steps at https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#creating-a-crash-report, thanks!

@hansmannj thanks for confirming, can you also share the extension logs when launching with --crash-reporter-directory, I am not sure why the flag to avoid the crash.

thanks for helping investigate. It's more likely that whatever operation came after those logs caused the crash since the error was caught and logged for 3.5 and 3.7. Is there another interpreter in /usr/include/, and can you check if it's a valid symlink? You could try running that same command for it too:

/usr/include/python* -I ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/interpreterInfo.py

Were you able to check in the Developer tools console as well? An extension host crash should show up in there. Developer: Toggle Developer Tools

As for the DEV tools console: yes and no. I switched it on and could see the console logs, but as the GUI completely freezes, I cannot scroll in the console's output or copy from it. But I managed to take a screenshot of the final output, just before the crash.

And a /usr/include/python* -I ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2023.6.1/pythonFiles/interpreterInfo.py yields a permission denied: /usr/include/python3.10

This is all pythons in the folder:

drwxr-xr-x   4 root root  12K Dez 14 08:44 python3.10
lrwxrwxrwx   1 root root   10 Feb 20  2021 python3.5 -> python3.5m
drwxr-xr-x   2 root root  12K Jan 21  2022 python3.5m
lrwxrwxrwx   1 root root   10 Aug 18  2020 python3.7 -> python3.7m
drwxr-xr-x   3 root root  16K Dez  7 20:09 python3.7m
drwxr-xr-x   4 root root  16K Dez  7 20:09 python3.9

Sorry, still did not have time to try a rollback. To what version do you recommend me to roll back?

Can other users facing the crash also try to get the crash logs following the steps at https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#creating-a-crash-report, thanks!

@hansmannj thanks for confirming, can you also share the extension logs when launching with --crash-reporter-directory, I am not sure why the flag to avoid the crash.

When I start in crash dump mode with code --crash-reporter-directory /home/USERNAME/local_dev/TEMPDELTE/VSCODE, there's nothing written to that specified folder, but vscode runs without freezing.

The most recent extension host logs in that case are:

2023-04-20 07:21:18.467 [info] Extension host with pid 19880 started
2023-04-20 07:21:18.467 [info] Skipping acquiring lock for /home/USERNAME/.config/Code/User/workspaceStorage/c45dd695cd1a86185e8038645a3a44f1.
2023-04-20 07:21:18.761 [info] ExtensionService#_doActivateExtension Vue.volar, startup: false, activationEvent: 'onLanguage:plaintext'
2023-04-20 07:21:18.811 [info] ExtensionService#_doActivateExtension vscode.emmet, startup: false, activationEvent: 'onLanguage'
2023-04-20 07:21:18.819 [info] ExtensionService#_doActivateExtension amazonwebservices.aws-toolkit-vscode, startup: false, activationEvent: 'onLanguage:python'
2023-04-20 07:21:19.363 [info] ExtensionService#_doActivateExtension batisteo.vscode-django, startup: false, activationEvent: 'onLanguage:python'
2023-04-20 07:21:19.375 [info] ExtensionService#_doActivateExtension KevinRose.vsc-python-indent, startup: false, activationEvent: 'onLanguage:python'
2023-04-20 07:21:19.378 [info] ExtensionService#_doActivateExtension ms-python.python, startup: false, activationEvent: 'onLanguage:python', root cause: ms-python.isort
2023-04-20 07:21:19.465 [info] ExtensionService#_doActivateExtension ms-toolsai.jupyter, startup: false, activationEvent: 'onLanguage:python'
2023-04-20 07:21:19.544 [info] ExtensionService#_doActivateExtension njpwerner.autodocstring, startup: false, activationEvent: 'onLanguage:python'
2023-04-20 07:21:19.567 [info] ExtensionService#_doActivateExtension VisualStudioExptTeam.intellicode-api-usage-examples, startup: false, activationEvent: 'onLanguage:python'
2023-04-20 07:21:19.656 [info] ExtensionService#_doActivateExtension VisualStudioExptTeam.vscodeintellicode, startup: false, activationEvent: 'onLanguage:python'
2023-04-20 07:21:21.296 [info] ExtensionService#_doActivateExtension vscode.git-base, startup: true, activationEvent: '*', root cause: vscode.git
2023-04-20 07:21:21.300 [info] ExtensionService#_doActivateExtension redhat.vscode-yaml, startup: true, activationEvent: '*', root cause: 42Crunch.vscode-openapi
2023-04-20 07:21:21.388 [info] ExtensionService#_doActivateExtension arcsine.chronicler, startup: true, activationEvent: '*'
2023-04-20 07:21:21.409 [info] ExtensionService#_doActivateExtension christian-kohler.path-intellisense, startup: true, activationEvent: '*'
2023-04-20 07:21:21.448 [info] ExtensionService#_doActivateExtension cssho.vscode-svgviewer, startup: true, activationEvent: '*'
2023-04-20 07:21:21.471 [info] ExtensionService#_doActivateExtension dariofuzinato.vue-peek, startup: true, activationEvent: '*'
2023-04-20 07:21:21.473 [info] ExtensionService#_doActivateExtension formulahendry.auto-close-tag, startup: true, activationEvent: '*'
2023-04-20 07:21:21.475 [info] ExtensionService#_doActivateExtension formulahendry.auto-rename-tag, startup: true, activationEvent: '*'
2023-04-20 07:21:21.485 [info] ExtensionService#_doActivateExtension yzhang.markdown-all-in-one, startup: true, activationEvent: 'workspaceContains:README.md'
2023-04-20 07:21:22.005 [info] ExtensionService#_doActivateExtension ms-toolsai.jupyter-renderers, startup: false, activationEvent: 'api', root cause: ms-toolsai.jupyter
2023-04-20 07:21:22.291 [info] ExtensionService#_doActivateExtension vscode.markdown-math, startup: false, activationEvent: 'api', root cause: yzhang.markdown-all-in-one
2023-04-20 07:21:22.335 [info] ExtensionService#_doActivateExtension vscode.github-authentication, startup: false, activationEvent: 'onAuthenticationRequest:github'
2023-04-20 07:21:22.470 [info] ExtensionService#_doActivateExtension ms-python.isort, startup: false, activationEvent: 'onLanguage:python'
2023-04-20 07:21:22.491 [info] ExtensionService#_doActivateExtension ms-python.vscode-pylance, startup: false, activationEvent: 'onLanguage:python'
2023-04-20 07:21:22.709 [info] ExtensionService#_doActivateExtension vscode.git, startup: true, activationEvent: '*'
2023-04-20 07:21:22.756 [info] ExtensionService#_doActivateExtension vscode.github, startup: true, activationEvent: '*'
2023-04-20 07:21:22.990 [info] ExtensionService#_doActivateExtension bierner.markdown-emoji, startup: false, activationEvent: 'api', root cause: yzhang.markdown-all-in-one
2023-04-20 07:21:23.202 [info] ExtensionService#_doActivateExtension marp-team.marp-vscode, startup: false, activationEvent: 'api', root cause: yzhang.markdown-all-in-one
2023-04-20 07:21:23.490 [info] ExtensionService#_doActivateExtension vscode.microsoft-authentication, startup: false, activationEvent: 'onAuthenticationRequest:microsoft'
2023-04-20 07:21:23.846 [info] ExtensionService#_doActivateExtension 42Crunch.vscode-openapi, startup: true, activationEvent: '*'
2023-04-20 07:21:24.150 [info] ExtensionService#_doActivateExtension mermade.openapi-lint, startup: true, activationEvent: '*'
2023-04-20 07:21:24.829 [warning] [redhat.vscode-yaml] Accessing a resource scoped configuration without providing a resource is not expected. To get the effective value for '[yaml]', provide the URI of a resource or 'null' for any resource.
2023-04-20 07:21:24.862 [info] Eager extensions activated
2023-04-20 07:21:24.961 [warning] [redhat.vscode-yaml] Accessing a resource scoped configuration without providing a resource is not expected. To get the effective value for '[yaml]', provide the URI of a resource or 'null' for any resource.
2023-04-20 07:21:25.012 [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: false, activationEvent: 'onStartupFinished'
2023-04-20 07:21:25.015 [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'
2023-04-20 07:21:25.022 [info] ExtensionService#_doActivateExtension amodio.toggle-excluded-files, startup: false, activationEvent: 'onStartupFinished'
2023-04-20 07:21:25.026 [info] ExtensionService#_doActivateExtension dbaeumer.vscode-eslint, startup: false, activationEvent: 'onStartupFinished'
2023-04-20 07:21:25.037 [info] ExtensionService#_doActivateExtension eamodio.gitlens, startup: false, activationEvent: 'onStartupFinished'
2023-04-20 07:21:25.073 [info] ExtensionService#_doActivateExtension vscode.npm, startup: false, activationEvent: 'onStartupFinished', root cause: esbenp.prettier-vscode
2023-04-20 07:21:25.082 [info] ExtensionService#_doActivateExtension GitHub.vscode-pull-request-github, startup: false, activationEvent: 'onStartupFinished'
2023-04-20 07:21:25.131 [info] ExtensionService#_doActivateExtension ms-vsliveshare.vsliveshare, startup: false, activationEvent: 'onStartupFinished'
2023-04-20 07:21:25.273 [info] ExtensionService#_doActivateExtension streetsidesoftware.code-spell-checker, startup: false, activationEvent: 'onStartupFinished'
2023-04-20 07:21:25.707 [warning] [redhat.vscode-yaml] Accessing a resource scoped configuration without providing a resource is not expected. To get the effective value for '[yaml]', provide the URI of a resource or 'null' for any resource.
2023-04-20 07:21:26.404 [info] ExtensionService#_doActivateExtension esbenp.prettier-vscode, startup: false, activationEvent: 'onStartupFinished'
2023-04-20 07:21:31.523 [error] {"message":"Git relative path not found."}

and the exported DEV Tools console output is in that case:

workbench.desktop.main.js:620  WARN 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.
workbench.desktop.main.js:620  WARN 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.
workbench.desktop.main.js:620  WARN 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.
workbench.desktop.main.js:620  WARN 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.
workbench.desktop.main.js:620  WARN [redhat.vscode-commons]: Cannot register 'redhat.telemetry.enabled'. This property is already registered.
workbench.desktop.main.js:620  WARN [redhat.vscode-yaml]: Cannot register 'redhat.telemetry.enabled'. This property is already registered.
workbench.desktop.main.js:620  WARN [Vue.volar]: Cannot register 'typescript.tsdk'. This property is already registered.
workbench.desktop.main.js:646 Ignoring vscode-kubernetes.kubectl-path.windows as vscode-kubernetes.kubectl-path is ""
(anonymous) @ workbench.desktop.main.js:646
workbench.desktop.main.js:646 Ignoring vscode-kubernetes.helm-path.windows as vscode-kubernetes.helm-path is ""
(anonymous) @ workbench.desktop.main.js:646
workbench.desktop.main.js:646 Ignoring vscode-kubernetes.minikube-path.windows as vscode-kubernetes.minikube-path is ""
(anonymous) @ workbench.desktop.main.js:646
workbench.desktop.main.js:646 Ignoring vscode-kubernetes.kubectl-path.mac as vscode-kubernetes.kubectl-path is ""
(anonymous) @ workbench.desktop.main.js:646
workbench.desktop.main.js:646 Ignoring vscode-kubernetes.helm-path.mac as vscode-kubernetes.helm-path is ""
(anonymous) @ workbench.desktop.main.js:646
workbench.desktop.main.js:646 Ignoring vscode-kubernetes.minikube-path.mac as vscode-kubernetes.minikube-path is ""
(anonymous) @ workbench.desktop.main.js:646
workbench.desktop.main.js:646 Ignoring vscode-kubernetes.kubectl-path.linux as vscode-kubernetes.kubectl-path is ""
(anonymous) @ workbench.desktop.main.js:646
workbench.desktop.main.js:646 Ignoring vscode-kubernetes.helm-path.linux as vscode-kubernetes.helm-path is ""
(anonymous) @ workbench.desktop.main.js:646
workbench.desktop.main.js:646 Ignoring vscode-kubernetes.minikube-path.linux as vscode-kubernetes.minikube-path is ""
(anonymous) @ workbench.desktop.main.js:646
workbench.desktop.main.js:1904 Overwriting grammar scope name to file mapping for scope source.python.
Old grammar file: file:///usr/share/code/resources/app/extensions/python/syntaxes/MagicPython.tmLanguage.json.
New grammar file: file:///home/USERNAME/.vscode/extensions/magicstack.magicpython-1.1.0/grammars/MagicPython.tmLanguage
register @ workbench.desktop.main.js:1904
workbench.desktop.main.js:1904 Overwriting grammar scope name to file mapping for scope source.yaml.
Old grammar file: file:///usr/share/code/resources/app/extensions/yaml/syntaxes/yaml.tmLanguage.json.
New grammar file: file:///home/USERNAME/.vscode/extensions/redhat.vscode-yaml-1.12.2/syntaxes/yaml.tmLanguage.json
register @ workbench.desktop.main.js:1904
workbench.desktop.main.js:1904 Overwriting grammar scope name to file mapping for scope source.vue.
Old grammar file: file:///home/USERNAME/.vscode/extensions/vue.volar-1.2.0-linux-x64/syntaxes/vue.tmLanguage.json.
New grammar file: file:///home/USERNAME/.vscode/extensions/wscats.vue-1.0.26/syntaxes/vue-generated.json
register @ workbench.desktop.main.js:1904
workbench.desktop.main.js:90 [Extension Host] Message Unavailable in region didn't get externalized correctly.
T @ workbench.desktop.main.js:90
workbench.desktop.main.js:620  WARN [mainThreadStorage] large extension state detected (extensionId: ms-toolsai.jupyter, global: true): 870.6982421875kb. Consider to use 'storageUri' or 'globalStorageUri' to store this data on disk instead.
workbench.desktop.main.js:90 [Extension Host] Message {0} Toolkit didn't get externalized correctly.
T @ workbench.desktop.main.js:90
workbench.desktop.main.js:620  WARN [mainThreadStorage] large extension state detected (extensionId: ms-toolsai.jupyter, global: true): 870.6982421875kb. Consider to use 'storageUri' or 'globalStorageUri' to store this data on disk instead.
workbench.desktop.main.js:84 [40b] potential listener LEAK detected, having 175 listeners already. MOST frequent listener (1):
check @ workbench.desktop.main.js:84
workbench.desktop.main.js:84 Error
    at i.create (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:84:31904)
    at l.l [as onDidChangeSelectedNotebooks] (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:86:1071)
    at o.$addKernel (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1586:34228)
    at m.N (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1593:15228)
    at m.M (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1593:14946)
    at m.H (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1593:14039)
    at m.G (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1593:13020)
    at vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1593:11808
    at g.invoke (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:86:145)
    at o.deliver (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:86:2121)
    at a.fire (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:86:1729)
    at u.fire (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:556:15210)
    at G.onmessage (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1691:1489)
check @ workbench.desktop.main.js:84
workbench.desktop.main.js:90 [Extension Host] Message {0} Remote Invocations didn't get externalized correctly.
T @ workbench.desktop.main.js:90
workbench.desktop.main.js:620  INFO [perf] Render performance baseline is 104ms
workbench.desktop.main.js:90 [Extension Host] Extension "openapi-lint" activated. 11
workbench.desktop.main.js:90 [Extension Host] openapi-lint: Installed save handler
workbench.desktop.main.js:620   ERR [Extension Host] (node:19880) [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)
workbench.desktop.main.js:90 [Extension Host] (node:19880) [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)
T @ workbench.desktop.main.js:90
workbench.desktop.main.js:90 [Extension Host] Message Add regions to {0} Explorer... didn't get externalized correctly.
T @ workbench.desktop.main.js:90
workbench.desktop.main.js:90 [Extension Host] Message Click here to add a region to {0} Explorer. didn't get externalized correctly.
T @ workbench.desktop.main.js:90
workbench.desktop.main.js:90 [Extension Host] rejected promise not handled within 1 second: Git relative path not found. {}
T @ workbench.desktop.main.js:90
$logExtensionHostMessage @ workbench.desktop.main.js:1593
N @ workbench.desktop.main.js:1593
M @ workbench.desktop.main.js:1593
H @ workbench.desktop.main.js:1593
G @ workbench.desktop.main.js:1593
(anonymous) @ workbench.desktop.main.js:1593
invoke @ workbench.desktop.main.js:86
deliver @ workbench.desktop.main.js:86
fire @ workbench.desktop.main.js:86
fire @ workbench.desktop.main.js:556
G.onmessage @ workbench.desktop.main.js:1691
workbench.desktop.main.js:620   ERR Git relative path not found.
workbench.desktop.main.js:1690 Extension Host
workbench.desktop.main.js:1690 Debugger attached.
workbench.desktop.main.js:620  INFO UNRESPONSIVE extension host: starting to profile NOW
workbench.desktop.main.js:620  INFO UNRESPONSIVE extension host: received responsive event and cancelling profiling session
DevTools failed to load source map: Could not load content for https://ticino.blob.core.windows.net/sourcemaps/704ed70d4fd1c6bd6342c436f1ede30d1cff4710/core/vs/workbench/workbench.desktop.main.js.map: Load canceled due to load timeout
workbench.desktop.main.js:620  INFO UNRESPONSIVE extension host: received responsive event and cancelling profiling session
workbench.desktop.main.js:620  INFO UNRESPONSIVE extension host: starting to profile NOW
workbench.desktop.main.js:1690 Extension Host
workbench.desktop.main.js:1690 Debugger attached.
workbench.desktop.main.js:620  WARN UNRESPONSIVE extension host: 'ms-python.python' took 21.259418912305648% of 188.101ms, saved PROFILE here: 'file:///tmp/exthost-8a2891.cpuprofile'
workbench.desktop.main.js:620  WARN UNRESPONSIVE extension host: 'ms-python.python' took 55.38582138113201% of 474.091ms, saved PROFILE here: 'file:///tmp/exthost-cb0205.cpuprofile'
workbench.desktop.main.js:90 [Extension Host] rejected promise not handled within 1 second: Git relative path not found. {}
T @ workbench.desktop.main.js:90
$logExtensionHostMessage @ workbench.desktop.main.js:1593
N @ workbench.desktop.main.js:1593
M @ workbench.desktop.main.js:1593
H @ workbench.desktop.main.js:1593
G @ workbench.desktop.main.js:1593
(anonymous) @ workbench.desktop.main.js:1593
invoke @ workbench.desktop.main.js:86
deliver @ workbench.desktop.main.js:86
fire @ workbench.desktop.main.js:86
fire @ workbench.desktop.main.js:556
G.onmessage @ workbench.desktop.main.js:1691
workbench.desktop.main.js:620   ERR Git relative path not found.

Again, thanks @amunger and @deepak1556 for checking this. Have a nice [time of day in your timezone]!

Something is going wrong with kernel discovery as shown from these logs.

workbench.desktop.main.js:620  WARN [mainThreadStorage] large extension state detected (extensionId: ms-toolsai.jupyter, global: true): 870.6982421875kb. Consider to use 'storageUri' or 'globalStorageUri' to store this data on disk instead.
workbench.desktop.main.js:90 [Extension Host] Message {0} Toolkit didn't get externalized correctly.
T @ workbench.desktop.main.js:90
workbench.desktop.main.js:620  WARN [mainThreadStorage] large extension state detected (extensionId: ms-toolsai.jupyter, global: true): 870.6982421875kb. Consider to use 'storageUri' or 'globalStorageUri' to store this data on disk instead.
workbench.desktop.main.js:84 [40b] potential listener LEAK detected, having 175 listeners already. MOST frequent listener (1):
check @ workbench.desktop.main.js:84
workbench.desktop.main.js:84 Error
    at i.create (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:84:31904)
    at l.l [as onDidChangeSelectedNotebooks] (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:86:1071)
    at o.$addKernel (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1586:34228)
    at m.N (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1593:15228)
    at m.M (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1593:14946)
    at m.H (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1593:14039)
    at m.G (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1593:13020)
    at vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1593:11808
    at g.invoke (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:86:145)
    at o.deliver (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:86:2121)
    at a.fire (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:86:1729)
    at u.fire (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:556:15210)
    at G.onmessage (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1691:1489)

Could you set "jupyter.logging.level": "verbose" and share the full jupyter.log again after reproing the issue (sorry for so many log requests!). Should be within the folder opened by the Developer: open extension logs folder command. You'll probably have to attach the file rather than pasting the contents because of the size.

Sorry for my late reply. Actually, the output is not too long, so I'll just paste it below. Not sure though, if the logging level really remained set to "verbose", or if that setting got lost during the crash. I only have a few seconds to set the logging level to verbose and open the extensions log folder, before the GUI beomes non-responsive..

Visual Studio Code (1.77.3, undefined, desktop)
Jupyter Extension Version: 2023.3.1201040234.
Python Extension Version: 2023.6.1.
Workspace folder /home/USERNAME/local_dev/Pythonkurs/py-tutorial
User belongs to experiment group 'jupyterEnhancedDataViewer'
User belongs to experiment group 'jupyterTestcf'
info 21:05:27.134: LSP Notebooks experiment is enabled
info 21:05:27.744: Process Execution: > ~/.virtualenvs/py-tutorial-AMwnrh1R/bin/python -m pip list
> ~/.virtualenvs/py-tutorial-AMwnrh1R/bin/python -m pip list
info 21:05:32.375: Starting Jupyter Session startUsingPythonInterpreter, .jvsc74a57bd0d2f426bb47ce91d0545fea9dd1955ca8cceecc50d47be4839a6d7a287da53a8f./home/USERNAME/.virtualenvs/py-tutorial-AMwnrh1R/python./home/USERNAME/.virtualenvs/py-tutorial-AMwnrh1R/python.-m#ipykernel_launcher (Python Path: /home/USERNAME/.virtualenvs/py-tutorial-AMwnrh1R, EnvType: PipEnv, EnvName: 'py-tutorial-AMwnrh1R', Version: 3.10.6 (main, Aug  2 2022, 15:11:28) [GCC 9.4.0]) for '/home/USERNAME/local_dev/Pythonkurs/py-tutorial/TEMP/geopandas.ipynb' (disableUI=true)
info 21:05:32.412: Process Execution: > ~/.virtualenvs/py-tutorial-AMwnrh1R/bin/python -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
> ~/.virtualenvs/py-tutorial-AMwnrh1R/bin/python -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
info 21:05:32.484: Process Execution: > ~/.virtualenvs/py-tutorial-AMwnrh1R/bin/python -m ipykernel_launcher --ip=127.0.0.1 --stdin=9018 --control=9016 --hb=9015 --Session.signature_scheme="hmac-sha256" --Session.key=b"b4eda0a7-6dea-4ede-8383-7877910d156f" --shell=9017 --transport="tcp" --iopub=9019 --f=/home/USERNAME/.local/share/jupyter/runtime/kernel-v2-205172ERcb6czmA1R.json
> ~/.virtualenvs/py-tutorial-AMwnrh1R/bin/python -m ipykernel_launcher --ip=127.0.0.1 --stdin=9018 --control=9016 --hb=9015 --Session.signature_scheme="hmac-sha256" --Session.key=b"b4eda0a7-6dea-4ede-8383-7877910d156f" --shell=9017 --transport="tcp" --iopub=9019 --f=/home/USERNAME/.local/share/jupyter/runtime/kernel-v2-205172ERcb6czmA1R.json
info 21:05:32.484: Process Execution: cwd: ~/local_dev/Pythonkurs/py-tutorial/TEMP
cwd: ~/local_dev/Pythonkurs/py-tutorial/TEMP
info 21:05:32.712: ipykernel version & path 6.21.3, ~/.virtualenvs/py-tutorial-AMwnrh1R/lib/python3.10/site-packages/ipykernel/__init__.py for /home/USERNAME/.virtualenvs/py-tutorial-AMwnrh1R/bin/python
warn 21:05:33.130: StdErr from Kernel Process /home/USERNAME/.virtualenvs/py-tutorial-AMwnrh1R/lib/python3.10/site-packages/traitlets/traitlets.py:2548: FutureWarning: Supporting extra quotes around strings is deprecated in traitlets 5.0. You can use 'hmac-sha256' instead of '"hmac-sha256"' if you require traitlets >=5.
  warn(

warn 21:05:33.131: StdErr from Kernel Process /home/USERNAME/.virtualenvs/py-tutorial-AMwnrh1R/lib/python3.10/site-packages/traitlets/traitlets.py:2499: FutureWarning: Supporting extra quotes around Bytes is deprecated in traitlets 5.0. Use 'b4eda0a7-6dea-4ede-8383-7877910d156f' instead of 'b"b4eda0a7-6dea-4ede-8383-7877910d156f"'.
  warn(

info 21:05:33.319: Started Kernel py-tutorial-AMwnrh1R (Python 3.10.6) (pid: 21404)
info 21:05:39.523: Process Execution: > ~/.virtualenvs/py-tutorial-AMwnrh1R/bin/python ~/.vscode/extensions/ms-toolsai.jupyter-2023.3.1201040234/pythonFiles/printJupyterDataDir.py
> ~/.virtualenvs/py-tutorial-AMwnrh1R/bin/python ~/.vscode/extensions/ms-toolsai.jupyter-2023.3.1201040234/pythonFiles/printJupyterDataDir.py
info 21:05:50.106: Shutting down notebooks for ac614827-53b4-44f8-8800-6a84649bac57
info 21:05:50.106: Disposing HostJupyterExecution 6ff6f22b-ea03-468b-bee7-e8104dbc6a60
info 21:05:50.106: Dispose Kernel '/home/USERNAME/local_dev/Pythonkurs/py-tutorial/TEMP/geopandas.ipynb' associated with '/home/USERNAME/local_dev/Pythonkurs/py-tutorial/TEMP/geopandas.ipynb'
info 21:05:50.109: Dispose Kernel process 21404.
info 21:05:50.138: Disposing HostJupyterExecution 6ff6f22b-ea03-468b-bee7-e8104dbc6a60
warn 21:05:50.464: Failed to delete connection file /home/USERNAME/.local/share/jupyter/runtime/kernel-v2-205172ERcb6czmA1R.json for pid 21404 Canceled (FileSystemError): Canceled
    at Function.c (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:100:27162)
    at Object.stat (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:100:25263)
    at Hu.delete (/home/USERNAME/.vscode/extensions/ms-toolsai.jupyter-2023.3.1201040234/out/extension.node.js:17:17182)
    at /home/USERNAME/.vscode/extensions/ms-toolsai.jupyter-2023.3.1201040234/out/extension.node.js:17:60879 {
  code: 'Unknown'
}

Does this help?

It looks like it's still just set to log info. Can you just directly edit the settings.json file before opening any files to activate the extension, Open User Settings (JSON), and add in "jupyter.logging.level": "verbose"

This issue seems to be resolved when I updated to the up-to-date VScode version.

Here is my environmental info:

Version: 1.78.0 Commit: 252e5463d60e63238250799aef7375787f68b4ee Date: 2023-05-03T20:09:46.685Z Electron: 22.4.8 Chromium: 108.0.5359.215 Node.js: 16.17.1 V8: 10.8.168.25-electron.0 OS: Linux x64 5.19.0-41-generic Sandboxed: Yes

I WAS having a similar problem after updating to version 1.78.2.

My Previous VS code version: 1.67.2 (I always turn off auto update when I get a stable version)

I used to run VSCode 1.67.2(system mode) installed in C/Program Files. I had to install PICO c/C++ SDK, which automatically installed VSCode-1.78.2 in User Mode(C:Users/AppData/Local)(It installed the User version concurrently). Prior to that, I used 1.67.2 in System mode with no issues. Unfortunately, due to the update, Jupyter extension has stopped working in both User mode and system mode installations. I even un-installed the User version of VS code and updated System version to 1.78.2 but no joy.

My jupyter notebook extension version: v2022.4.1021342353

AFTER UPDATING(completely uninstall all jupyter related extensions and re-install them{updated versions} back) MY JUPYTER EXTENSION, THE PROBLEM WAS SOLVED.

Uninstall and re-install all the above extensions. (Uninstall "Gather" extension FIRST, if you have it, and re-install it LAST(after updating all jupyter extensions mentioned above)).

CPUs | Intel(R) Core(TM) i3-8145U CPU @ 2.10GHz (4 x 2304) -- | -- GPU Status | 2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled Load (avg) | Memory (System) | 7.78GB (1.11GB free) Process Argv | --crash-reporter-id 138af8b6-eb47-4f68-a9e6-7dd18ead6ddf Screen Reader | no VM | 0%

closing as fixed since we haven't heard from anyone still experiencing crashes on the latest version

microsoft / vscode-jupyter