VScode keeps crashing after update

[abuonau]

Type: Performance Issue

As soon as I load a file the window freezes and I get the message that the windows does not respond

VS Code version: Code 1.81.1 (6c3e3dba23e8fadc360aed75ce363ba185c49794, 2023-08-09T22:20:33.924Z) OS version: Darwin x64 22.6.0 Modes:

System Info

|Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-8559U CPU @ 2.70GHz (8 x 2700)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
metal: disabled_off
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)|5, 4, 5| |Memory (System)|16.00GB (4.78GB free)| |Process Argv|| |Screen Reader|no| |VM|0%|

Process Info

``` CPU % Mem MB PID Process 19 360 4039 code main 0 49 4043 gpu-process 0 16 4045 utility-network-service 0 98 4081 shared-process 0 0 4849 /bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command= 0 197 4826 window [4] (Welcome) 0 49 4828 fileWatcher [4] 0 82 4829 extensionHost [4] 0 82 4842 window [5] (Issue Reporter) ```

Workspace Info

``` ; ```

Extensions (18)

Extension|Author (truncated)|Version ---|---|--- vscode-django|bat|1.10.0 python-environment-manager|don|1.0.4 python-extension-pack|don|1.7.0 remotehub|Git|0.60.0 vsc-python-indent|Kev|1.18.0 python|ms-|2023.14.0 vscode-pylance|ms-|2023.8.30 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 azure-repos|ms-|0.36.0 remote-repositories|ms-|0.38.1 autodocstring|njp|0.6.1 intellicode-api-usage-examples|Vis|0.2.7 vscodeintellicode|Vis|1.2.30 jinja|who|0.0.8

A/B Experiments

``` vsliv368cf:30146710 vsreu685:30147344 python383cf:30185419 vspor879:30202332 vspor708:30202333 vspor363:30204092 vslsvsres303:30308271 vserr242cf:30382550 pythontb:30283811 vsjup518:30340749 pythonptprofiler:30281270 vshan820:30294714 vstes263cf:30335440 vscoreces:30445986 vscod805cf:30301675 binariesv615:30325510 bridge0708:30335490 bridge0723:30353136 vsaa593cf:30376535 pythonvs932:30410667 vsclangdf:30486550 c4g48928:30535728 dsvsc012cf:30540253 pynewext54:30695312 azure-dev_surveyone:30548225 vscccc:30803845 2e4cg342:30602488 89544117:30613380 showlangstatbar:30737416 03d35959:30757346 pythonfmttext:30731395 pythoncmv:30756943 fixshowwlkth:30771522 showindicator:30805244 pythongtdpath:30769146 i26e3531:30792625 gsofa:30804715 pythonnosmt12:30797651 pythonidxptcf:30805731 pythonnoceb:30805159 dsvsc013:30795093 dsvsc014:30804076 diffeditorv1:30812748 ```

[gjsjohnmurray]

/confirmPlease

[vscodenpa]

Please perform the following three tasks to diagnose the root cause of the issue:

• [ ] 1.) Disable Extensions

  • Select View and pick Command Palette...
  • Run Developer: Reload With Extensions Disabled
  • 👉 See if the issue reproduces

• [ ] 2.) Disable Configuration

  • Select View and pick Command Palette...
  • Run Profiles: Create a Temporary Profile
  • 👉 See if the issue reproduces

• [ ] 3.) Try VS Code Insiders

  • Download VS Code Insiders
  • Install and Run it
  • 👉 See if the issue reproduces

Then pick one of the three resolutions depending on which step has helped:

Disabling my Extensions helped

Please run the command `Start Extension Bisect` and follow the instructions to find the extension that is causing this issue. Please report the issue to the extension causing this.

Disabling my configuration helped

Please report back more details about your configuration, including settings.

Using VS Code Insiders has helped

✅ This likely means that the issue has been addressed already and will be available in an upcoming release. You can safely use VS Code Insiders until the new stable version is available.

[abuonau]

This is what happens. I will try what you suggested and report.

[abuonau]

The issue reproduces in all three cases. I had also tried to reinstall VS code from scratch but nothing changed

[abuonau]

I solved the issue. I am sorry if I have wasted your time. The problem was on my side. The file I was loading was too big. I realised when I tried to open a different file. It was just a coincidence this happened after the update.