Vscode-gitlens: Extension host terminated unexpectedly - Message always appearing

Created on 27 Feb 2018  路  8Comments  路  Source: eamodio/vscode-gitlens


Hi there! I am receiving this annoying error once VSCode was opened:

image

You may see additional details on https://github.com/Microsoft/vscode/issues/44265

  • GitLens Version:
    image

  • VSCode Version:
    image

  • OS Version:
    Windows 10 Enterprise

Steps to Reproduce:

As seen on https://github.com/Microsoft/vscode/issues/44265

  1. Updated VSCode to January 2018 (version 1.20)
  2. Installed GitLens
needs more info

All 8 comments

Hrm, first I would suggest uninstalling GitLens, restarting vscode (twice), and then re-installing GitLens, to rule out any installation issues.

If the issue still persists after that, with no extensions enabled other than GitLens, can you enable logging to see if anything shows up? You can enable output channel logging by setting "gitlens.outputLevel": "verbose" in your settings.json. This will enable logging to the GitLens channel in the Output pane. Once enabled, please attempt to reproduce the issue (if possible) and attach the relevant log lines from the GitLens channel.

@KBPsystem777 Can you retry with the latest GitLens version and see if you are still experiencing this issue?

@eamodio trying now, will get back here for feedback :)

@eamodio issue seems to be resolved. I just updated GitLens to new version, restarted VSCode and the error message didnt showed up again. I waited 2 days but so far, no message is showing up :)

Great! Glad to hear it. I'm going to close this then. Please reopen if it comes back.

I am getting this error and I am getting this error after having latest update of VS code. I am running react native. The non-react-native people are not getting that error.

@itsmasud can you follow the steps here: https://github.com/eamodio/vscode-gitlens/issues/298#issuecomment-368944503 and post back?

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Was this page helpful?
0 / 5 - 0 ratings