vscode: VSCode freezes/blocks at startup

Hello,

VSCode is very long to start, juste showing a blank window for up to 10 sec. Sometimes, I also have a popup window proposing to kill/restart or wait. Also, after VSCode is finally started, after a couple of minutes, it freezes for again few seconds (10-20) before being fully operationnal. This behavior only concern the 1st open window. If I open a new one, no issue. Also, if I close all the open windows, and then open again VSCode, the issue is reproduced.

I have tried tu play with different options like --disable-extensions and --disable-gpu, but without any improvements… I have also tried to fully remove VSCode and the extensions, and then reinstall, but I still have the same behavior.

My system is:

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.4 LTS
Release:	22.04
Codename:	jammy
$ uname -a
Linux LPFR0237 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb  9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

System Info

  • Code: 1.87.0 (019f4d1419fbc8219a181fab7892ebccf7ee29a2)
  • OS: linux(6.5.0-21-generic)
  • CPUs: 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz(8 x 4075)
  • Memory(System): 31.06 GB(27.07GB free)
  • Memory(Process): 284.92 MB working set(194.28MB private, 0.97MB shared)
  • VM(likelihood): 0%
  • Initial Startup: true
  • Has 0 other windows
  • Screen Reader Active: false
  • Empty Workspace: false

Attached profiling files (with option --prof-startup)

prof-uwGrxS2H.renderer.cpuprofile.txt prof-uwGrxS2H.main.cpuprofile.txt

Attached generated report (with option --prof-startup)

report.md

About this issue

  • Original URL
  • State: open
  • Created 4 months ago
  • Reactions: 2
  • Comments: 16 (5 by maintainers)

Most upvoted comments

I’m having insane performance generally since 1.87 and have had to download 1.86.2 and turn off automatic updates. It doesn’t freeze on startup necessarily but the whole thing slows to a crawl and basically freezes very shortly. Was thinking maybe it was placebo, but before turning off updates, it started happening again and realised it’s because I had updated again… so I know I’m not going mad

Hi, Any news on this ticket? Any other idea?