|Extension|Author|Version|
|---|---|---|
|jslint|ajhyndman|1.2.1|
|html-class-suggestions|AndersEAndersen|1.0.7|
|vscode-database|bajdzis|1.2.0|
|vscode-styled-jsx|blanu|0.1.0|
|vscode-javascript-snippets|codepunkt|1.0.0|
|jshint|dbaeumer|0.10.15|
|jquerysnippets|donjayamanne|0.0.1|
|theme-dracula|dracula-theme|1.9.1|
|vscode-babel-coloring|dzannotti|0.0.4|
|vscode-html-css|ecmel|0.1.1|
|react-native-react-redux|EQuimper|0.2.0|
|prettier-vscode|esbenp|0.13.0|
|php-intellisense|felixfbecker|1.1.5|
|javascript-unit-test-snippet|iZDT|1.0.0|
|react-component|jeremyrajan|1.0.0|
|cobalt2-Theme|kamranmackey|0.0.3|
|format-php|Kasik96|1.1.2|
|vscode-JS-CSS-HTML-formatter|lonefy|0.2.3|
|language-vscode-javascript-angular2|nwallace|0.0.11|
|ejs-language-support|QassimFarid|0.0.1|
|vscode-format|ryannaddy|0.0.6|
|react-beautify|taichi|0.3.0|
|jsx|TwentyChung|0.0.1|
|jsx-snippets|TwentyChung|0.0.1|
|expresssnippet|vladmrnv|0.1.0|
|vscode-react-native|vsmobile|0.3.2|
|JavaScriptSnippets|xabikos|1.4.0|;
Steps to Reproduce:
1.VS Code sends message Error Extension host terminated unexpectedly. Please reload to recover!
shell.ts:475 Invalid string length: RangeError: Invalid string length
at Object.r [as stringify] (c:\Program Files (x86)\Microsoft VS Code\resourcesapp\out\vs\workbenchnode\extensionHostProcess.js:4:38622)
at Function.e.request (c:\Program Files (x86)\Microsoft VS Code\resourcesapp\out\vs\workbenchnode\extensionHostProcess.js:4:136194)
at Object.callOnRemote (c:\Program Files (x86)\Microsoft VS Code\resourcesapp\out\vs\workbenchnode\extensionHostProcess.js:4:134903)
at t._callOnRemote (c:\Program Files (x86)\Microsoft VS Code\resourcesapp\out\vs\workbenchnode\extensionHostProcess.js:4:278169)
at Object.$updateGroupResourceStates (c:\Program Files (x86)\Microsoft VS Code\resourcesapp\out\vs\workbenchnode\extensionHostProcess.js:4:277734)
at e.set [as resourceStates] (c:\Program Files (x86)\Microsoft VS Code\resourcesapp\out\vs\workbenchnode\extensionHostProcess.js:4:337633)
at GitSCMProvider.onDidModelChange (c:\Program Files (x86)\Microsoft VS Code\resourcesapp\extensions\git\out\scmProvider.js:88:46)
at i (c:\Program Files (x86)\Microsoft VS Code\resourcesapp\extensions\git\out\util.js:44:83)
at e.invoke (c:\Program Files (x86)\Microsoft VS Code\resourcesapp\out\vs\workbenchnode\extensionHostProcess.js:4:16423)
at e.fire (c:\Program Files (x86)\Microsoft VS Code\resourcesapp\out\vs\workbenchnode\extensionHostProcess.js:4:20054)
I'm also facing same issue. And after I get that error every package no longer work
It is been like this for last few days
I meet that problem again.
#24748
@ddzmitry Does this happen for folders that aren't under git version control?
@jrieken Happend for both git folder and not a git folder
@jrieken Both
@ddzmitry Where did you find that message? Can you share a screenshot?
@ngohungphuc Can you share a screenshot too?
@joaomoreno
This is what I get when open developer console
@ngohungphuc Can you also try out our insider release?
@joaomoreno Same error
@joaomoreno the same error , and same picture
@ngohungphuc @ddzmitry Does this happen on any folder you open with Code? Even if you open a brand new window without any open folder?
@ngohungphuc Yes it does. even with Insider

It happens to me too
I created an issue with issue id 24914. Attached is a screenshot
Since I started getting the error, I've been tempted to switch editors. Its really disturbing
@PolymathWhiz Sorry about that. Are you willing to do a screen sharing session right now with me, so we figure out what's wrong?
https://hangouts.google.com/hangouts/_/joaomoreno.com/vscode17475
cc @ngohungphuc @ddzmitry Any of you guys can also join in, I would love to get some help on this, as I fail to repro on any of my machines.
Currently not in the position to do that
But I can provide written aid
Just had an awesome chat with @ddzmitry, and we figured out that his issue is that he had a folder open which wasn't a git repository while at the same time there was a git repository in his home folder. This caused Code to handle that git repository which had many many active changes.
This is definitely a dupe of #23976, I'll try to get a fix out today. The fix will try to catch these huge repository issues before they break the extension host.
The workaround for you guys is, which is the right fix:
git rev-parse --show-toplevel. This will tell you where the root of the git repository you have opened is..git folder.Once again, thanks @ddzmitry for your help!
@joaomoreno Anytime! Thank you!
@joaomoreno please push the fix and let's make vscode better, together!
@joaomoreno thank you! the workaround is working fine:)
Waiting for the fix.This error drive me crazy for a week
- Open the workspace folder in a shell and type
git rev-parse --show-toplevel. This will tell you where the root of the git repository you have opened is.- Evaluate whether this repository should exist or not. In @ddzmitry's case it was his user's home, which made no sense. He fixed it by simply removing that
.gitfolder.
@ngohungphuc Can you look at these steps? They are the right fix.
@joaomoreno I think when I try to open multiple folder in vs code that contain multiple .git folder it will break extension host
@ngohungphuc The permanent fix will likely come as an update soon
Thank you guys
@PolymathWhiz The _permanent_ fix is a warning that you have opened a folder in a git repo that has too many active changes, so features will be limited. Prior to April, the Git features were disabled altogether.
Overall, it would be great if you could confirm that your scenario is indeed what I described above:
git repository which had many many active changes
Fixed by 0be6167d9ed4c9c67a14e0250c768f4283bf54e5
The latest insider update already has this fixed, care to give it a try?
@joaomoreno vscode 1.12.0 also have this problem
@ joamoreno vscode 1.12.0 also have this problem
I have also encountered this problem


still has the same problem with Version 1.15.1
Most helpful comment
Just had an awesome chat with @ddzmitry, and we figured out that his issue is that he had a folder open which wasn't a git repository while at the same time there was a git repository in his home folder. This caused Code to handle that git repository which had many many active changes.
This is definitely a dupe of #23976, I'll try to get a fix out today. The fix will try to catch these huge repository issues before they break the extension host.
The workaround for you guys is, which is the right fix:
git rev-parse --show-toplevel. This will tell you where the root of the git repository you have opened is..gitfolder.Once again, thanks @ddzmitry for your help!