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

Extension host terminated unexpectedly in vs code insiders 1.31.0 #250

Closed
minoseah629 opened this issue Dec 14, 2018 · 50 comments
Closed

Extension host terminated unexpectedly in vs code insiders 1.31.0 #250

minoseah629 opened this issue Dec 14, 2018 · 50 comments

Comments

@minoseah629
Copy link

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Feature request
[ ] Documentation issue or request
[ ] Other: <!-- Please describe: -->

Current behavior

After launching vscode-insider and a moment later, I get Extension host terminated unexpectedly.

I disabled all extensions with no issue.
I reenabled all extensions and located developer tool and saw below error:

Developer Tool shows this error:

dyld: lazy symbol binding failed: Symbol not found: __ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorENS_14SideEffectTypeE
Referenced from: /Users/xxx/.vscode-insiders/extensions/ritwickdey.liveserver-5.3.1/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node
Expected in: flat namespace

Expected behavior

VS Code operates normally

Environment

Browser:

no applicable browser

For Tooling issues:

- Live Server: 5.3.1
- Platform:  10.14.3 Beta (18D21c)
- Visual Studio Code: Version 1.31.0-insider (1.31.0-insider)

Others

microsoft/vscode#64981

@hassanbinsafdar
Copy link

Same Here :(

@kouhei
Copy link

kouhei commented Dec 15, 2018

same problem

@ritwickdey ritwickdey pinned this issue Dec 16, 2018
@ritwickdey
Copy link
Owner

Hey, sorry for late. Seems like it's a serious issue. Can anyone please share console of vscode (Help => Toggle Develoer Tools) ?

@ritwickdey
Copy link
Owner

Sorry, I got the log from @minoseah629

@ritwickdey
Copy link
Owner

The issue is comes from fsevents. Seems like all of you're using Mac.

There are some breaking changes as vscode-insider is now using electron.js v3.x and Node.js 10.x

The Issue is related to electron/electron#14841 & fsevents/fsevents#229

I've upgraded one package. Can anyone please clone the project & install the package from here

Please let me know if you need any help to manual install and status of extension after install ?

@kouhei
Copy link

kouhei commented Dec 16, 2018

I don't know how to install the extension from here.
Please let me know it.

@ritwickdey
Copy link
Owner

Hi @kouhei thanks for your interest. Sorry for a late reply (due to my exams).

Can you join with me in Hangout Text Chat or Skype Text Chat (or anyone ? )

Hangout: ritwickdey97@gmail.com
Skype: ritwickdey

[It'll be annoying if I do chat here, because everyone will receive emails for every comment.]

@abdohossam5
Copy link

any chance of fixing this soon. it's making the insiders edition unusable.

@davidpurnell
Copy link

manually updating to v5.4.0-alpha fixed this for me...

@bengry
Copy link

bengry commented Dec 21, 2018

@ritwickdey I tried to manually install the vsix in the releases, as well as manually compiling from the source code of the alpha2 tag, in both I get the follow error when trying to use the extension, the extension host doesn't seem to be crashing though:
image

@kristofferR
Copy link

kristofferR commented Jan 7, 2019

It's still not fixed, I tried installing LiveServer-5.4.0-alpha4-osx.vsix and Extension Host is still crashing:

dyld: lazy symbol binding failed: Symbol not found: __ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorENS_14SideEffectTypeE
  Referenced from: /Users/kristoffer/.vscode-insiders/extensions/ritwickdey.liveserver-5.4.0-alpha4/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node
  Expected in: flat namespace

dyld: Symbol not found: __ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorENS_14SideEffectTypeE
  Referenced from: /Users/kristoffer/.vscode-insiders/extensions/ritwickdey.liveserver-5.4.0-alpha4/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node
  Expected in: flat namespace

@Ceus
Copy link

Ceus commented Jan 8, 2019

Still failing on 1.31.0-insider (1.31.0-insider).

extension host

Extension Host                   /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:3273

dyld: lazy symbol binding failed: Symbol not found: __ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorENS_14SideEffectTypeE
  Referenced from: /Users/jfelps/.vscode-insiders/extensions/ritwickdey.liveserver-5.3.1/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node
  Expected in: flat namespace

dyld: Symbol not found: __ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorENS_14SideEffectTypeE
  Referenced from: /Users/jfelps/.vscode-insiders/extensions/ritwickdey.liveserver-5.3.1/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node
  Expected in: flat namespace

@crystalfp
Copy link

Idem in 1.30.2 But I used it (together with Live SCSS compiler) before this upgrade.
Hope it helps.

@rjoydip-zz rjoydip-zz unpinned this issue Jan 20, 2019
@markonyango
Copy link

Version: 1.30.2 (system setup) Commit: 61122f88f0bf01e2ac16bdb9e1bc4571755f5bd8 Datum: 2019-01-07T22:54:13.295Z Electron: 2.0.12 Chrome: 61.0.3163.100 Node.js: 8.9.3 V8: 6.1.534.41 Betriebssystem: Windows_NT x64 10.0.17134

Same here. I fire up VS Code and the extension host crashes immediately.

@adesugbaa
Copy link
Collaborator

adesugbaa commented Jan 30, 2019

Please try 5.4.0 release build.

@kristofferR
Copy link

Please try 5.4.0 release build.

Still doesn't work.
capto_capture 2019-02-04_03-59-22_am

@ritwickdey ritwickdey pinned this issue Feb 5, 2019
@adesugbaa
Copy link
Collaborator

adesugbaa commented Feb 6, 2019

Please try 5.4.0 release build.

Still doesn't work.
capto_capture 2019-02-04_03-59-22_am

Please provide information on OS, VS Code Build etc.

Are you running the latest build of Visual Code Insiders? Please retry the 5.4.0 build once you update to the latest nightly build from yesterday.

@rebeccapeltz
Copy link

I'm seeing the extension host crash too.

@mrjjwright
Copy link

Crashing for me as well with VSCode 1.31 release

@mrjjwright
Copy link

Nevermind, working when I manually installled 1.5.4 from VSIX file.

@hckdbrd
Copy link

hckdbrd commented Feb 7, 2019

Live server uninstalling let me get rid of that strange issue. Try to uninstall it! Good Luck!

@llauderesv
Copy link

Hi I'm also experiencing this issue.

Hope will fix it as soon as possible.

VS Code Version 1.31.0

screen shot 2019-02-07 at 9 15 41 am

@minoseah629
Copy link
Author

It worked for v 1.32.0-insider

@adesugbaa
Copy link
Collaborator

Please download 5.4.0 from this repo (under Releases), and try installing that manually.

View -> Command Pallete... -> Extensions Install from VSIX...

Select the extension you downloaded, and restart VS Code when it completes.

Please provide feedback - 5.4.0 will be published once we confirm it is working for all.

@kristofferR
Copy link

The latest 5.4.0 version now works fine, on macOS and VS Code 1.32.0 👍

@ritwickdey ritwickdey unpinned this issue Feb 7, 2019
@ritwickdey
Copy link
Owner

Please install v5.4.0 from marketplace. Let us know if it doesn't work. (and also don't forget to update vscode-insider 😄)

@leoggonzalez
Copy link

leoggonzalez commented Feb 12, 2019

This is also happening in vs code v1.31

I tried installing the v5.4.0 from the marketplace but the issue persisted. Also tried vscode-insiders but no luck.

I had to rollback to vscode 1.30 :(

@ritwickdey
Copy link
Owner

Hi @leoggonzalez, Have you tried the lastest version? It should work.

Anyway, is this same issue? you can create a new issue request in GitHub if the issue is different.

@crystalfp
Copy link

crystalfp commented Feb 12, 2019 via email

@philipaarseth
Copy link

This Is still a problem, using the insiders version is by no means a fix. It doesn't even use the same settings.

@Ceus
Copy link

Ceus commented Feb 12, 2019

This is resolved for me.

Version 1.32.0-insider (1.32.0-insider)
Live Server v5.5.1

@crystalfp
Copy link

OK, waiting for new Code and Live server versions. In the mean time I simply run sass --wait outside Code.

@hevisko
Copy link

hevisko commented Apr 2, 2019

Same issue on Version 1.32.3 (1.32.3)

dyld: lazy symbol binding failed: Symbol not found: __ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorENS_14SideEffectTypeE
  Referenced from: /Users/hvisage/.vscode/extensions/living42.vscode-simple-sync-0.0.1/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node
  Expected in: flat namespace

dyld: Symbol not found: __ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorENS_14SideEffectTypeE
  Referenced from: /Users/hvisage/.vscode/extensions/living42.vscode-simple-sync-0.0.1/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node
  Expected in: flat namespace

@GuoZhiQiang
Copy link

I disable all the Extensions , then enable them one by one and find that Settings Sync extension caused the error :Extension host terminated unexpectedly.. Finally I disable Settings Sync solve the problem. But I really want to use Settings Sync. Feeling bad.

My VSCode version : 1.33.0.

@aziez
Copy link

aziez commented Apr 9, 2019

I disable all the Extensions , then enable them one by one and find that Settings Sync extension caused the error :Extension host terminated unexpectedly.. Finally I disable Settings Sync solve the problem. But I really want to use Settings Sync. Feeling bad.

My VSCode version : 1.33.0.

all fixs with disable setting sync

@ricardorojass
Copy link

I disable all the Extensions , then enable them one by one and find that Settings Sync extension caused the error :Extension host terminated unexpectedly.. Finally I disable Settings Sync solve the problem. But I really want to use Settings Sync. Feeling bad.

My VSCode version : 1.33.0.

Thanks, works for me

@TepyThai
Copy link

If updating Live-Server doesn't work for you, try "disable" "Setting sync" extension.

@paoloalmeida
Copy link

WOW! Thank you so much! It works for me :)

@daisyleenr
Copy link

I disable all the Extensions , then enable them one by one and find that Settings Sync extension caused the error :Extension host terminated unexpectedly.. Finally I disable Settings Sync solve the problem. But I really want to use Settings Sync. Feeling bad.

My VSCode version : 1.33.0.

Thanks, works for me :)

@TunvirRahman
Copy link

deleting all extension of VSCode help me to solve the issue.
cd ~/.vscode/extensions and then delete all and now reinstall your required extensions again

@danlafreniere
Copy link

Disabling settings sync also worked for me. Thank you!

@datajunkee
Copy link

I tried disabling, didn't work. I then tried deleting all extensions and restarted...naturally it worked. Then installing just Live Server causes the Extension host failure with the following message:

Screen Shot 2019-04-17 at 5 01 30 AM

@TunvirRahman
Copy link

Caused by Settings Sync extension. I was using React Native Full Pack extension and this extension is using Settings Sync extension as dependency. So I have switched to another Extension named React Native Tools and now Solved the issue.

@jonathaniqueda
Copy link

When I disable Live Server extension, resolved for me.

@BashirAljounaidy
Copy link

deleting all extension of VSCode help me to solve the issue.
cd ~/.vscode/extensions and then delete all and now reinstall your required extensions again

Thank youuu . Done

@MaksymilianWojcik
Copy link

The simplest solution is to disable all extensions and enable them all again :) Also did the same with Live Server - reenabling solved the issue, I can still use it

@ritwickdey
Copy link
Owner

ritwickdey commented Apr 17, 2019

New version is published. Please try to install from store. It should work. If not, please let me know.

Thank you so much to all of you for reporting here :)

@KaceAlexiCasey
Copy link

Guys, the problem is in your code if that problem appears. For example I used a path of a deleted folder somwhere in my .scss files and this issue started the crash of the Sass Live Compiler.

Just check your code for any strange errors.

@cuongdevjs
Copy link

just only disable or uninstall extension live-sass, it's work for me
Hope help.

@devarajuavula
Copy link

devarajuavula commented Jul 25, 2019

I tried all the above step and procedures but there is no solution.
finally, I Cross checked all my installed extensions plugins and I found same and similar extensions twice or trice the problem will be occurs. So, I uninstall the related or similar extension plugins like "TODO" the problem is solved. Thank you
Todo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests