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 stops in VSCODE #104

Closed
TimSoethout opened this issue Feb 25, 2019 · 9 comments
Closed

Extension host stops in VSCODE #104

TimSoethout opened this issue Feb 25, 2019 · 9 comments
Labels

Comments

@TimSoethout
Copy link

I get this error message in the developer console when opening an argdown file in VSCode, or trying to visualize one.

extensionService.ts:457 Extension host terminated unexpectedly. Code:  null  Signal:  SIGABRT
t._onExtensionHostCrashed @ extensionService.ts:457
notificationsAlerts.ts:40 Extension host terminated unexpectedly.
t.onDidNotificationChange @ notificationsAlerts.ts:40
extensionHost.ts:231 Extension Host
extensionHost.ts:232 dyld: lazy symbol binding failed: Symbol not found: __ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorENS_14SideEffectTypeE
  Referenced from: /Users/tim/.vscode/extensions/christianvoigt.argdown-vscode-1.0.5/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/tim/.vscode/extensions/christianvoigt.argdown-vscode-1.0.5/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node
  Expected in: flat namespace

Is this a known error? Or maybe related to other VSCode plugins?

@TimSoethout
Copy link
Author

Maybe related to this: microsoft/vscode#68024

@TimSoethout
Copy link
Author

As per mentions bug link, i downgraded to vscode 1.30 and it seems to work again.

https://code.visualstudio.com/updates/v1_30

@christianvoigt
Copy link
Owner

thank you for finding this out and reporting it here, I was not aware of it. I have subscribed to the issue and will follow the discussion.

@ggbetz
Copy link
Collaborator

ggbetz commented Feb 25, 2019

I can confirm Tim's report. The problem started to occur with one of the last updates of VS code.

dyld: lazy symbol binding failed: Symbol not found: __ZN2v816FunctionTemplate3NewEPNS_7IsolateEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEENS_5LocalIS4_EENSA_INS_9SignatureEEEiNS_19ConstructorBehaviorENS_14SideEffectTypeE
  Referenced from: /Users/ggbetz/.vscode/extensions/christianvoigt.argdown-vscode-1.0.5/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/ggbetz/.vscode/extensions/christianvoigt.argdown-vscode-1.0.5/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64/fse.node
  Expected in: flat namespace

@Myself5
Copy link

Myself5 commented Feb 26, 2019

The same issue has been observed and fixed here: ritwickdey/vscode-live-server#250

Looks like it's caused by the Electron and NodeJS updates in 1.31 (and above), which is why downgrading to 1.30.2 fixes the issue.

Judging by ritwickdey/vscode-live-server#267, ritwickdey/vscode-live-server@ca594e4 seems to fix this issue.

@christianvoigt
Copy link
Owner

Thanks for the help! So it seems updating Chokidar/fsevents will fix this. I had planned to work on Argdown this week anyway so you won't have to wait long for the next release.

@hevisko
Copy link

hevisko commented Apr 2, 2019

Same issue with Version 1.32.3 (1.32.3)

@christianvoigt
Copy link
Owner

christianvoigt commented Apr 3, 2019

Hi, thanks for the notification, I have just tested this myself. I did update chokidar in the last release (which depends on fsevents), but apparently at the time chokidar had not updated fsevents and was still using 1.2.7 even though chokidar did update fsevents to version 1.2.7 it does not fix this. There were a lot of changes in the last release, so I forgot to test this again. Sorry for that.

Chokidar has updated fsevents to the new napi version in 3.0.0-pre but this is not released yet. Not sure what to do right now.

@christianvoigt
Copy link
Owner

christianvoigt commented Apr 3, 2019

@hevisko can you please go to your ~/vscode/extensions folder and check if there are two versions of argdown-vscode? In my case deleting the older version fixed the issue.

VSCode told me that it had updated the extension, but the error message was still coming from the old version. So I guess there was something wrong with the update process.

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

No branches or pull requests

5 participants