Change:
disturl "https://atom.io/download/electron" <del> target "9.2.0" </del> <ins> target "9.2.1" </ins> runtime "electron"

Discussion:
latest VS Code insiders, turn on Voice Over on mac P -notice how the screen reader does not read any of the items in the quick pick This works just fine on Linux and Windows. Also works fine for stable. So it seems like an chrome update in electron broke this I can also repro running in . In Firefox and Safari all is good. I can not reproduce in Chrome cannary, so there seems to be a fix in Chrome latest. Ideally we would find the fix in Chrome and backport it to our Electron. fyi And for Chrome smartness, maybe one of your collegues fixed something like this (should be related to )
I can add this to my list (which is starting to grow I'm afraid). BUT, you don't need smartness; you need the most excellent bisect-build tool! :smile: Docs here: Once you have the regression range, you just sit there as pre-built binaries are presented for you to try and mark as good or bad. Best. Tool. Ever. Lemme know if you have any questions or need help.
Thanks a lot. Let's see if already has this set up, otherwise I can also look into it.
Yup I can do the bisect shortly.
Bisect result for when regression was introduced: Potential candidate: https://chromium-
Looking for fix now.
Upstream fix: https://chromium- Crbug:
Impressive. Thanks a lot!

<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --<!-- Use Help Report Issue to prefill these. --- VSCode Version: don't know, I uninstalled it OS Version: ubuntu 20.04 Steps to Reproduce: on icon code insiders opens and closes right away I tried rebooting, uninstall/reinstall, still crashes (probably not related, but slack recently started doing exact same crash) <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No I don't know how.
I'm also getting the same problem using snap. Stable with snap works fine, had the crash after updating. Ubuntu 20.04. Logs:
thanks for the logs, seeing the gpu process crashed eventually, can you try running with ?
weird that gpu process is still crashing. Can you try launching with . If it still crashes, launch with and attach the crash dump generated.
fyi, nothing saves to /tmp/vscode-crash if that is .
Thanks for the logs Its good to know that software compositing is attempted to be used, without crash dumps its hard to understand whats happening in the gpu process. Let me look into fixing and then we can proceed from there. One more thing to try, can you paste the output of
This appears to be a snap issue. I uninstalled the snap () and re-installed via ppa and apt (instructions: ) and it is working fine.
I am trying to repro this issue on my machine today, I am running Ubuntu 18.04 on parallels vm , installed insiders with . Opening the app via command line or via app icon doesn't seem to generate any crash. Is there something I am missing in the setup ?
Possibly Ubuntu 20.04
I got crash on ubuntu 18.04 so its not just 20.04
I can try on 20.04 is there any difference in my setup from yours ?
I crash on both command line and app icon. Running dual boot with windows 10 rn. No VM. Possible it has to do with hardware too.

Thanks for the details, one more thing to confirm, does it crash when you run from deb or tar packages of insiders
Laptop HP ProBook 455R G6 8VT74EA (AMD Ryzen 7 3700U, AMD Radeon Rx Vega 10) Linux Mint 20 (Ubuntu 20.04, Kernel 5.4.0-42) Cinnamon 4.6.6 snap 2.45.2 <details<summaryVS Code output</summary</details
My co-worker and I both had the July 22nd snap update start failing at the same time (). They were running Ubuntu 18.04 and Gnome, while I was running 20.04 and i3 on metal, not a VM. We both have GPUs. Given the GPU and /dev/fd/3 errors I question whether a VM with emulated hardware would produce the same errors as metal with an actual GPU. Just a thought.
I just tried 20.04 on my parallels, haven't seen any crash so far. So yeah I need to try this without a VM. can you confirm if the crash doesn't occur when you use the deb or tar packages of the insiders , the installation you had linked in is an external repo not maintained by vscode, not sure if the insiders you had tested there are on the same runtime Electron
no crash when installing from .deb package
Same
Thanks all for the details, I will setup the required environment to repro the crash in the upcoming days. We have pushed electron 9 update to next milestone (August 2020), insiders from tomorrow will be on Electron 7 which shouldn't crash with the snap builds.
Update VS Code from <details<summaryVS Code output</summary</details
the revision you had tested is still on , please test latest revision
Thank you, , this revision works.
Insiders started crashing for me again. Did electron 9 get pushed to insiders again?
VS Code Insiders crashes again <details<summaryVS Code output</summary</details
I can confirm this issue. OS: Ubuntu 20.04.1 DE: Gnome 3.36.

4 vs code-insiders: (via snap) -vscode-insiders --verbose /usr/lib/x8664-linux- undefined symbol: gdatetimeformatiso8601 Failed to load module: /usr/lib/x8664-linux- [(52)] expecting appcenter url prefix [main 2020-08-20T11:40:18.346Z] Starting VS Code [main 2020-08-20T11:40:18.347Z] from: /snap/code-insiders/504/usr/share/code-insiders/resources/app [main 2020-08-20T11:40:18.347Z] args: { : [], diff: false, add: false, goto: false, 'new-window': false, 'reuse-window': false, wait: false, help: false, 'list-extensions': false, 'show-versions': false, version: false, verbose: true, status: false, 'prof-startup': false, 'disable-extensions': false, 'disable-gpu': false, telemetry: false, logExtensionHostCommunication: false, 'skip-release-notes': false, 'disable-restore-windows': false, 'disable-telemetry': false, 'disable-updates': false, 'disable-crash-reporter': false, 'crash-reporter-id': '-383a-460d-a034-', 'disable-user-env-probe': 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, 'open-devtools': false, 'no-proxy-server': false, nolazy: false, 'force-renderer-accessibility': false, 'ignore-certificate-errors': false, 'allow-insecure-localhost': false } [main 2020-08-20T11:40:18.349Z] Resolving machine identifier. [main 2020-08-20T11:40:18.349Z] Resolved machine identifier: 3d40557f33209ef8cfa811b6385cb272885c22dabcab665043134c086c599a78 [main 2020-08-20T11:40:18.

366Z] update#setState idle [main 2020-08-20T11:40:18.374Z] [storage ] open( - , retryOnBusy: true) [main 2020-08-20T11:40:18.375Z] lifecycle (main): phase changed (value: 2) [main 2020-08-20T11:40:18.376Z] windowsManager#open [main 2020-08-20T11:40:18.378Z] window#validateWindowState: validating window state on 1 display(s) { mode: 1, x: 1611, y: 407, width: 1069, height: 810 } [main 2020-08-20T11:40:18.379Z] window#validateWindowState: 1 monitor working area { x: 0, y: 21, width: 3072, height: 1707 } [main 2020-08-20T11:40:18.379Z] window#ctor: using window state { mode: 1, x: 1611, y: 407, width: 1069, height: 810 } [(52)] expecting appcenter url prefix [main 2020-08-20T11:40:18.456Z] lifecycle (main): phase changed (value: 3) [main 2020-08-20T11:40:18.458Z] telemetry/optInStatus { optIn: true } [main 2020-08-20T11:40:18.459Z] telemetry/machineIdFallback { usingFallbackGuid: false } [(52)] expecting appcenter url prefix [main 2020-08-20T11:40:18.495Z] [storage ] Trace (event): SELECT * FROM ItemTable [main 2020-08-20T11:40:18.496Z] [storage ] getItems(): 53 rows [(90)] glXGetFBConfigs failed. [(130)] Failed to get GLXConfig [(479)] CreateDummyWindow(gfx::GetXDisplay()) failed [(148)] GLSurfaceGLX::InitializeOneOff failed.

pci id for fd 29: 1002:15d8, driver (null) [(1520)] X error received: serial 432, errorcode 8 (BadMatch (invalid parameter attributes)), requestcode 78, minorcode 0 (XCreateColormap) [(152)] Exiting GPU process due to errors during initialization [(52)] expecting appcenter url prefix pci id for fd 29: 1002:15d8, driver (null) [main 2020-08-20T11:40:18.597Z] [storage ] updateItems(): insert(Map(3) {storage.serviceMachineId =-b103-43c6-b2c8-, telemetry.lastSessionDate =Thu, 20 Aug 2020 11:40:03 GMT, telemetry.currentSessionDate =Thu, 20 Aug 2020 11:40:18 GMT}), delete(Set(0) {}) [main 2020-08-20T11:40:18.598Z] [storage ] Trace (event): BEGIN TRANSACTION [main 2020-08-20T11:40:18.599Z] [storage ] Trace (event): INSERT INTO ItemTable VALUES ('storage.serviceMachineId','-b103-43c6-b2c8-'),('telemetry.lastSessionDate','Thu, 20 Aug 2020 11:40:03 GMT'),('telemetry.currentSessionDate','Thu, 20 Aug 2020 11:40:18 GMT') [main 2020-08-20T11:40:18.599Z] [storage ] Trace (event): END TRANSACTION /dev/fd/3: No such file or directory Server response: [(1222)] The GPU process has crashed 1 time(s) [(52)] expecting appcenter url prefix pci id for fd 28: 1002:15d8, driver (null) [(985)] Reinitialized the GPU process after a crash. The reported initialization time was 15 ms /dev/fd/3: No such file or directory Server response: [(1222)] The GPU process has crashed 2 time(s) [(52)] expecting appcenter url prefix pci id for fd 29: 1002:15d8, driver (null) [(985)] Reinitialized the GPU process after a crash.

The reported initialization time was 19 ms /dev/fd/3: No such file or directory Server response: [(1222)] The GPU process has crashed 3 time(s) [(52)] expecting appcenter url prefix pci id for fd 23: 1002:15d8, driver (null) [(985)] Reinitialized the GPU process after a crash. The reported initialization time was 0 ms [main 2020-08-20T11:40:19.217Z] getShellEnvironment: running on CLI, skipping /dev/fd/3: No such file or directory Server response: [(1222)] The GPU process has crashed 4 time(s) [(52)] expecting appcenter url prefix pci id for fd 27: 1002:15d8, driver (null) [(985)] Reinitialized the GPU process after a crash. The reported initialization time was 0 ms /dev/fd/3: No such file or directory Server response: [(1222)] The GPU process has crashed 5 time(s) [(52)] expecting appcenter url prefix pci id for fd 27: 1002:15d8, driver (null) [(985)] Reinitialized the GPU process after a crash. The reported initialization time was 0 ms /dev/fd/3: No such file or directory Server response: (node:4970) Electron: Loading non-context-aware native module in renderer: '/snap/code-insiders/504/usr/share/code-'. This is deprecated, see [(1222)] The GPU process has crashed 6 time(s) [(439)] GPU process isn't usable. Goodbye. (node:4970) Electron: Loading non-context-aware native module in renderer: '/snap/code-insiders/504/usr/share/code-'. This is deprecated, see /dev/fd/3: No such file or directory Server response: /dev/fd/3: No such file or directory Server response:
Some updates, I was able to setup the environment that repros the crash, after investigating the crash which was failing to load graphic libraries for libgbm, it turns out the build environment for snap we have been using was outdated Ubuntu 14.04. I updated the environment to 18.04 and here is the new , now its crashing with a mismatched glibc version error when run on ubuntu 20.04.

Anyone has idea on what could be the issue here
I have a possible workaround based on https://chromium-, will update here once new build is available for testing.
Tomorrow's insider will contain the fix, incase you want to check on a one time test build