vscode: Linux crash on startup in latest Insiders

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

Steps to Reproduce:

  1. Open VSCode, with or without disabling extensions or GPU
$ code-insiders --verbose --disable-extensions
[18286:0209/072339.822046:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
[main 2022-02-09T00:23:39.853Z] [File Watcher (node.js)] Request to start watching: /home/intrnl/.config/Code - Insiders/User (excludes: <none>),/home/intrnl/.config/Code - Insiders/User/settings.json (excludes: <none>)
[main 2022-02-09T00:23:39.875Z] Starting VS Code
[main 2022-02-09T00:23:39.876Z] from: /opt/visual-studio-code-insiders/resources/app
[main 2022-02-09T00:23:39.876Z] args: {
  _: [],
  diff: false,
  add: false,
  goto: false,
  'new-window': false,
  'reuse-window': false,
  wait: false,
  help: false,
  'list-extensions': false,
  'show-versions': false,
  'pre-release': false,
  version: false,
  verbose: true,
  status: false,
  'prof-startup': false,
  'no-cached-data': false,
  'prof-v8-extensions': false,
  'disable-extensions': true,
  'disable-gpu': false,
  'ms-enable-electron-run-as-node': false,
  telemetry: false,
  debugRenderer: false,
  logExtensionHostCommunication: false,
  'skip-release-notes': false,
  'skip-welcome': false,
  'disable-telemetry': false,
  'disable-updates': false,
  'disable-keytar': false,
  'disable-workspace-trust': false,
  'disable-crash-reporter': false,
  'skip-add-to-recently-opened': false,
  'unity-launch': false,
  'open-url': false,
  'file-write': false,
  'file-chmod': false,
  'driver-verbose': false,
  force: false,
  'do-not-sync': false,
  trace: false,
  'force-user-env': false,
  'force-disable-user-env': false,
  'open-devtools': false,
  __sandbox: false,
  'no-proxy-server': false,
  'no-sandbox': false,
  nolazy: false,
  'force-renderer-accessibility': false,
  'ignore-certificate-errors': false,
  'allow-insecure-localhost': false,
  logsPath: '/home/intrnl/.config/Code - Insiders/logs/20220209T072339'
}
[main 2022-02-09T00:23:39.877Z] Resolving machine identifier...
[main 2022-02-09T00:23:39.878Z] Resolved machine identifier: 58a15d6e1e5bf15a98458ace9d5f6d012ea3ce165535cb3c7ffbf98f320c6aab
[main 2022-02-09T00:23:39.880Z] Main->SharedProcess#connect
[main 2022-02-09T00:23:39.884Z] [File Watcher (node.js)] Started watching: '/home/intrnl/.config/Code - Insiders/User'
[main 2022-02-09T00:23:39.907Z] [File Watcher (node.js)] Error: ENOENT: no such file or directory, stat '/home/intrnl/.config/Code - Insiders/User/settings.json'
[main 2022-02-09T00:23:39.932Z] StorageMainService: creating global storage
[main 2022-02-09T00:23:39.940Z] lifecycle (main): phase changed (value: 2)
[main 2022-02-09T00:23:39.941Z] windowsManager#open
[main 2022-02-09T00:23:39.941Z] windowsManager#open pathsToOpen [ [Object: null prototype] {} ]
[main 2022-02-09T00:23:39.942Z] windowsManager#doOpenEmpty {
  restore: false,
  remoteAuthority: undefined,
  filesToOpen: undefined,
  forceNewWindow: false
}
[main 2022-02-09T00:23:39.944Z] IPC Object URL: Registered new channel vscode:e2743a9b-1672-470b-a911-c40bea70fa96.
[main 2022-02-09T00:23:39.944Z] window#validateWindowState: validating window state on 1 display(s) {
  width: 1024,
  height: 768,
  mode: 1,
  x: 256,
  y: 48,
  hasDefaultState: true
}
[main 2022-02-09T00:23:39.944Z] window#validateWindowState: 1 monitor working area { x: 0, y: 25, width: 1536, height: 839 }
[main 2022-02-09T00:23:39.944Z] window#ctor: using window state {
  width: 1024,
  height: 768,
  mode: 1,
  x: 256,
  y: 48,
  hasDefaultState: true
}
[main 2022-02-09T00:23:39.987Z] window#load: attempt to load window (id: 1)
[main 2022-02-09T00:23:39.999Z] windowsManager#open used window count 1 (workspacesToOpen: 0, foldersToOpen: 0, emptyToRestore: 0, emptyToOpen: 1)
[main 2022-02-09T00:23:40.001Z] lifecycle (main): phase changed (value: 3)
[main 2022-02-09T00:23:40.004Z] update#setState idle
[main 2022-02-09T00:23:40.005Z] resolveShellEnv(): skipped (VSCODE_CLI is set)

Works fine in yesterday’s build f8c36556a2c305327f5417dc7f93220f39ed608f

Verbose logging seems to stop here, and I’m not sure if it contains any particularly helpful information, is there any way I can get more out of it?

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 7
  • Comments: 27 (4 by maintainers)

Most upvoted comments

Thanks for the logs and testing with insiders, I was able to confirm the bug. Will update here once the fix has been pushed.

Insiders build crash on startup (ubuntu wayland) pending.zip

> code-insiders --disable-extensions --verbose

/usr/share/code-insiders/code-insiders --disable-extensions --verbose --enable-crashpad: symbol lookup error: /usr/share/code-insiders/resources/app/node_modules.asar.unpacked/vscode-encrypt/build/Release/vscode-encrypt-native.node: undefined symbol: SHA256_Init

That appears to be a regression in Electron due to debug symbols being enabled: https://github.com/electron/electron/issues/32669 (unrelated to the crashing issues)

Where can I download a previous version (.tar.gz, linux-x64), such as 1.65.0-1644314957 mentioned by @ultraheroe ?

  1. Go to https://packages.microsoft.com/repos/vscode/pool/main/c/code-insiders/
  2. Pick the wished version.
  3. Open a DEB file with Ark.
  4. Open data.tar.xz.
  5. Go to usr/share and extract only the folder code-insiders.
  6. Inside the extracted folder code-insiders, you click twice the code-insiders file.