5

I get this error after I clicked "Kill terminal" in VS Code:

"Unable to resolve your shell environment: Unexpected exit code from spawned shell (code null, signal SIGSEGV)"

enter image description here

Now my VSCode does this when I click on Terminal, New Terminal: It opens the window for about one second and then crashes and disappears.

I already deleted the settings.json file because I found a post on a similar problem. Unfortunately this did not help.

Finn
  • 161
  • 1
  • 14

3 Answers3

5

Simply restart the computer solved the issue for me (MacOS)

¯_(ツ)_/¯

Thilun
  • 51
  • 1
  • 2
1

I believe I got the same message and was definitely struggling with the same Terminal crashing issue. What worked for me was uninstalling VS Code, and then downloading it again.

I'm using macOS and surprisingly, all my extensions were still available in the reinstall. There's probably a more technical way of doing it but that worked for me so I hope that helps!

vijaivir
  • 36
  • 3
  • 1
    I also uninstalled VS Code multiple times. But that didn't seem to work. However everyone should try reinstalling VS Code first. Probably my way of uninstalling VS Code was inconvenient. – Finn Aug 22 '22 at 14:51
-1

I had this same issue. The issue was resolved for me after I updated VS Code.

Calvin Raab
  • 1
  • 2
  • This does not really answer the question. If you have a different question, you can ask it by clicking [Ask Question](https://stackoverflow.com/questions/ask). To get notified when this question gets new answers, you can [follow this question](https://meta.stackexchange.com/q/345661). Once you have enough [reputation](https://stackoverflow.com/help/whats-reputation), you can also [add a bounty](https://stackoverflow.com/help/privileges/set-bounties) to draw more attention to this question. - [From Review](/review/late-answers/32742567) – Rager Sep 22 '22 at 22:30