microsoft / microsoft/vscode

VS Code 1.136.0 crashes with SIGSEGV during startup on CachyOS/KDE Wayland

Open
#334,211 1 comment 1 reaction 1 assignee Claimed by @deepak1556 View on GitHub
Dominant language
TypeScript
Stars
193k
Forks
42.4k
PR merge metrics
PR metrics pending

Description

VS Code 1.136.0 crashes immediately during startup with a SIGSEGV on CachyOS Linux.

VS Code 1.135.0 works normally on the exact same system. Downgrading from 1.136.0 to 1.135.0 immediately resolves the crash.

The crash is reproducible even with a completely clean user data directory and with GPU acceleration disabled.

Environment:
- VS Code: 1.136.0
- Commit: 520fb30b2d3d324b4cb2342f6e88e2cd93751de1
- OS: CachyOS
- Kernel: 6.18.48-1-cachyos-lts
- Desktop Environment: KDE Plasma
- Session: Wayland
- Architecture: x86_64
- Installation: visual-studio-code-bin (AUR)
- glib2: 2.88.3-1.1
- gtk3: 3.24.52-1.1
- mesa: 26.2.2-2
- xorg-xwayland: 24.1.13-1.1

Steps to reproduce:

1. Install VS Code 1.136.0.
2. Run:

/usr/share/code/code --disable-gpu --ozone-platform=x11 --user-data-dir=/tmp/vscode-test --verbose

3. VS Code crashes immediately with SIGSEGV.

The crash also occurs without the --disable-gpu option.

Expected behavior:

VS Code should start normally.

Actual behavior:

VS Code crashes immediately with:

Segmentation fault (core dumped)

coredumpctl reports:

Signal: 11 (SEGV)
Executable: /usr/share/code/code

GDB backtrace:

#0 0x00007ffff3dacea0 in ?? ()
#1 0x00007ffff78c3977 in ?? () from /usr/lib/libgio-2.0.so.0
#2 0x00007ffff78c627e in ?? () from /usr/lib/libgio-2.0.so.0
#3 0x00007ffff784be2d in ?? () from /usr/lib/libgio-2.0.so.0
#4 0x00007ffff78c2c23 in ?? () from /usr/lib/libgio-2.0.so.0
#5 0x00007ffff7844178 in ?? () from /usr/lib/libgio-2.0.so.0
#6 0x00007ffff7e5df4d in ?? () from /usr/lib/libglib-2.0.so.0
#7 0x00007ffff7e5f478 in ?? () from /usr/lib/libglib-2.0.so.0
#8 0x00007ffff7e5f5d2 in g_main_context_iteration ()
from /usr/lib/libglib-2.0.so.0
#9 0x000055555881cd16 in ?? ()
#10 0x0000089800124420 in ?? ()
#11 0x0000000000000000 in ?? ()

Additional testing:

The crash is not related to my existing VS Code profile or extensions because it also occurs with:

--user-data-dir=/tmp/vscode-test

The crash also persists with:

--disable-gpu

Therefore, disabling GPU acceleration does not resolve the issue.

Regression:

- VS Code 1.135.0: works normally
- VS Code 1.136.0: crashes with SIGSEGV during startup

I downgraded the AUR package back to VS Code 1.135.0, and VS Code immediately started normally again on the same system.

This appears to be a regression introduced in or exposed by VS Code 1.136.0 on this Linux environment.

The backtrace shows the crash occurring through libgio-2.0.so.0 / libglib-2.0.so.0.

Please let me know if additional diagnostic information, a full core dump, or other testing is required.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.