Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VSCode Segfault when starting on Arch Linux #188254

Closed
FirelightFlagboy opened this issue Jul 19, 2023 · 4 comments
Closed

VSCode Segfault when starting on Arch Linux #188254

FirelightFlagboy opened this issue Jul 19, 2023 · 4 comments
Assignees
Labels
info-needed Issue requires more information from poster

Comments

@FirelightFlagboy
Copy link

Does this issue occur when all extensions are disabled?: Yes

Versions

  • VS Code Version:

    1.80.1
    74f6148eb9ea00507ec113ec51c489d6ffb4b771
    x64
  • OS Version:

    OS: Arch Linux x86_64
    Kernel: 6.4.3-arch1-2 
    DE: Hyprland

Notable configuration

{
  "password-store": "kwallet5",
  "enable-features": "UseOzonePlatform",
  "oxone-platform": "wayland",
  "enable-crash-reporter": true,
  "crash-reporter-id": "3c24d65b-3046-4b68-a003-e0c855714dd1"
}

Steps

I'm able to sometime reproduce the issue with the following steps:

  1. Start vscode (sometime it crash)

My point of view when it crash:

vscode open a window, then the window is close instantly

Logs

@zjeffer
Copy link

zjeffer commented Jul 24, 2023

Possibly a duplicate of #184124?

@deepak1556
Copy link
Collaborator

We don't support "enable-features" and "ozone-platform" in the runtime configure arguments, are you using a custom build of VSCode ? You would instead need to start with code --ozone-platform=wayland. Can you attach the crash report following the steps at https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#creating-a-crash-report

@deepak1556 deepak1556 added the info-needed Issue requires more information from poster label Jul 26, 2023
@FirelightFlagboy
Copy link
Author

FirelightFlagboy commented Jul 26, 2023

Are you using a custom build of VSCode ?

No, i'm using the aur package visual-studio-code-bin

Name            : visual-studio-code-bin
Version         : 1.80.1-1
Description     : Visual Studio Code (vscode): Editor for building and debugging modern web and cloud applications (official binary version)
Architecture    : x86_64
URL             : https://code.visualstudio.com/
Licenses        : custom: commercial
Groups          : None
Provides        : code  vscode
Depends On      : libxkbfile  gnupg  gtk3  libsecret  nss  gcc-libs  libnotify  libxss  glibc  lsof  shared-mime-info  xdg-utils  alsa-lib
Optional Deps   : glib2: Needed for move to trash functionality [installed]
                  libdbusmenu-glib: Needed for KDE global menu
                  org.freedesktop.secrets: Needed for settings sync [installed]
                  icu69: Needed for live share
Required By     : None
Optional For    : None
Conflicts With  : code
Replaces        : None
Installed Size  : 337,82 MiB
Packager        : Unknown Packager
Build Date      : 2023-07-17T08:32:58 CEST
Install Date    : 2023-07-17T08:33:11 CEST
Install Reason  : Explicitly installed
Install Script  : Yes
Validated By    : None

What do you mean by

We don't support enable-features and ozone-platform

? Did you mean that we can't configure those option in argv.json ?

For me it work as expected 🤔 vscode don't use xwayland

Maybe they work because I have ~/.config/code-flags.conf with the following content 🤔

--enable-features=UseOzonePlatform
--ozone-platform=wayland

Those parameters are from https://wiki.hyprland.org/Getting-Started/Master-Tutorial/#force-apps-to-use-wayland


Following https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#creating-a-crash-report

Without any other configuration other than running code with --crash-reporter-directory, I've the following dmp file inside the zip: vscode-crash-dump.zip

@deepak1556
Copy link
Collaborator

Did you mean that we can't configure those option in argv.json ?

Yes that is correct, the aur package possibly added support for reading those values from ~/.config/code-flags.conf which works in your case.

Thanks for the crash logs, the stack is similar to #184124, I will merge this issue.

@github-actions github-actions bot locked and limited conversation to collaborators Sep 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

5 participants