Closed ghuntley closed 7 years ago
Now it's working again.......
Additional information which may be relevant.
› brew list --versions
ack 2.14
archey 1.6.0
aria2 1.26.1
autoconf 2.69
automake 1.15
boost 1.61.0_1
dirmngr 1.1.1_2
dos2unix 7.3.4
elinks 0.11.7_2
freetype 2.7
gdbm 1.12
ghostscript 9.19
git 2.10.0
gnupg2 2.0.30_2
gpg-agent 2.0.30_1
htop-osx 0.8.2.8
imagemagick 6.9.5-9_2
jpeg 8d
jq 1.5_2
jsonpp 1.2.0
libassuan 2.4.3_1
libevent 2.0.22
libgcrypt 1.7.3
libgpg-error 1.24
libksba 1.3.5
libpng 1.6.25
libtiff 4.0.6_2
libtool 2.4.6_1
libusb 1.0.20
libusb-compat 0.1.5
libyaml 0.1.7
little-cms2 2.8
moreutils 0.60
ncftp 3.2.5
nginx 1.10.1
nmap 7.12
node 6.5.0
oniguruma 6.1.1_1
openssl 1.0.2h_1 1.0.2j
p7zip 16.02
pcre 8.39
pinentry 0.9.7
pkg-config 0.29.1_1 0.29.1_2
proxychains-ng 4.11
pth 2.0.7
python 2.7.12
readline 6.3.8 7.0
rpl 1.4.1
ruby 2.3.1_2
sqlite 3.14.2
tmux 2.3
wget 1.18
xz 5.2.2
youtube-dl 2016.09.11.1
zsh 5.2
@ghuntley from the output it looks like you had another instance of Code running (maybe a crashed process leftover?) that receives the request from the CLI to open a window and that probably failed. So next time this happens, maybe check the activity monitor for left over "Code" processes running.
@bpasero I had several instances of Code Helper
running. I killed all of them, but the last one restarts with a new PID every time I try to kill it. This seems to be causing vscode to crash on startup.
Steps to Reproduce:
Crashes when launching from GUI and also when launched from CLI
Have uninstalled and reinstalled via downloading from official website.