microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
162.78k stars 28.73k forks source link

Linter crashes #190389

Closed vanerk03 closed 1 year ago

vanerk03 commented 1 year ago

Type: Bug

When I use jupyter notebook, the linter crashes and nothing helps to restart it: restarting kernel/opening closing the file/editing the file. The only thing that helps is restarting vscode.

VS Code version: Code 1.81.1 (6c3e3dba23e8fadc360aed75ce363ba185c49794, 2023-08-09T22:22:42.175Z) OS version: Windows_NT x64 10.0.22621 Modes:

System Info |Item|Value| |---|---| |CPUs|AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx (8 x 2096)| |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)|undefined| |Memory (System)|6.94GB (1.71GB free)| |Process Argv|--crash-reporter-id 48ded65a-f1d8-413b-88ef-6a92d7e2ec57| |Screen Reader|no| |VM|0%|
Extensions (56) Extension|Author (truncated)|Version ---|---|--- calva|bet|2.0.383 calva-spritz|bet|1.0.4 doxdocgen|csc|1.4.0 c-cpp-compile-run|dan|1.0.49 make-hidden|dev|4.0.4 githistory|don|0.6.20 gitlens|eam|14.2.1 html-preview-vscode|geo|0.2.5 copilot|Git|1.101.317 vscode-github-actions|git|0.26.1 live-sass|gle|6.1.0 gc-excelviewer|Gra|4.2.57 latex-workshop|Jam|9.13.4 better-cpp-syntax|jef|1.17.2 cmake-language-support-vscode|jos|0.0.9 git-graph|mhu|1.30.0 vscode-docker|ms-|1.26.0 vscode-dotnet-runtime|ms-|1.6.0 isort|ms-|2023.10.1 python|ms-|2023.14.0 vscode-pylance|ms-|2023.8.20 jupyter|ms-|2023.7.1002162226 jupyter-keymap|ms-|1.1.2 jupyter-renderers|ms-|1.0.17 vscode-jupyter-cell-tags|ms-|0.1.8 vscode-jupyter-slideshow|ms-|0.1.5 remote-containers|ms-|0.304.0 remote-ssh|ms-|0.102.0 remote-wsl|ms-|0.81.0 cmake-tools|ms-|1.15.31 cpptools|ms-|1.17.1 cpptools-extension-pack|ms-|1.3.0 hexeditor|ms-|1.9.12 makefile-tools|ms-|0.7.0 remote-explorer|ms-|0.4.1 ppm-pgm-viewer-for-vscode|ngt|1.1.4 autodocstring|njp|0.6.1 material-icon-theme|PKi|4.29.0 prolog|reb|0.0.4 java|red|1.21.0 keep-a-changelog|RLN|1.3.0 rust-analyzer|rus|0.3.1615 markdown-preview-enhanced|shd|0.6.8 vscode-rustfmt|sta|0.1.2 snippets|tah|3.0.0 ayu|tea|1.0.5 cmake|twx|0.0.17 intellicode-api-usage-examples|Vis|0.2.7 vscodeintellicode|Vis|1.2.30 vscode-java-debug|vsc|0.53.0 vscode-java-dependency|vsc|0.23.1 vscode-java-pack|vsc|0.25.13 vscode-java-test|vsc|0.39.1 vscode-maven|vsc|0.42.0 vscode-todo-highlight|way|1.0.5 vscode-java-saber|You|0.1.2 (2 theme extensions excluded)
A/B Experiments ``` vsliv368cf:30146710 vsreu685:30147344 python383:30185418 vspor879:30202332 vspor708:30202333 vspor363:30204092 vswsl492cf:30256860 vstes516:30244333 vslsvsres303:30308271 vserr242cf:30382550 pythontb:30283811 vsjup518:30340749 pythonptprofiler:30281270 vshan820:30294714 vstes263:30335439 vscorecescf:30445987 vscod805:30301674 binariesv615:30325510 bridge0708:30335490 bridge0723:30353136 vsaa593cf:30376535 pythonvs932:30410667 py29gd2263cf:30792227 vsclangdf:30486550 c4g48928:30535728 dsvsc012:30540252 pynewext54:30695312 azure-dev_surveyone:30548225 vscccc:30803845 2e4cg342:30602488 89544117:30613380 showlangstatbar:30737416 03d35959:30757346 57b77579:30736110 pythonfmttext:30731395 pythoncmvfstrcf:30756944 fixshowwlkth:30771522 showindicator:30805244 pythongtdpath:30769146 i26e3531:30792625 gsofb:30804716 pythonnosmt12:30797651 pythonidxptcf:30805731 pythonnoceb:30805159 dsvsc013:30795093 dsvsc014:30804076 ```
gjsjohnmurray commented 1 year ago

/causedByExtension

VSCodeTriageBot commented 1 year ago

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. If you don't know which extension is causing the problem, you can run Help: Start extension bisect from the command palette (F1) to help identify the problem extension.

Happy Coding!