Live Sass Compiler causes Extension Host crash after latest VSCode update

[VAggrippino]

After today's VSCode update, Live Sass Compiler causes "Extension Host terminated unexpectedly" whenever I open a Sass file.

I don't know if it matters, but the Sass file I'm editing when it happens is part of a GitHub Pages Jekyll blog.

I'll attach the Extension Host log. Let me know if you need more information.

VSCode Info:

Version: 1.35.0 (system setup) Commit: 553cfb2c2205db5f15f3ee8395bbd5cf066d357d Date: 2019-06-04T01:17:12.481Z Electron: 3.1.8 Chrome: 66.0.3359.181 Node.js: 10.2.0 V8: 6.6.346.32 OS: Windows_NT x64 10.0.17134

VSCode_Extension-Host_crash_ritwickdey.live-sass-1559964197747.log

[art-frela]

Hello, I'm confirm, very often arise error Extension host terminated unexpectedly. Code: 7 I have VSCode installed on the three machines (Linux, MacOS, Win7) - and everywhere has that error.

/Users/Artem/.vscode/extensions/ritwickdey.live-sass-3.0.0/node_modules/sasslib/sass.sync.js:61
var Module=typeof Module!=="undefined"?Module:{};var moduleOverrides={};var key;for(key in Module){if(Module.hasOwnProperty(key)){moduleOverrides[key]=Module[key]}}Module["arguments"]=[];Module["thisProgram"]="./this.program";Module["quit"]=(function(status,toThrow){throw toThrow});Module["preRun"]=[];Module["postRun"]=[];var ENVIRONMENT_IS_WEB=false;var ENVIRONMENT_IS_WORKER=false;var ENVIRONMENT_IS_NODE=false;var ENVIRONMENT_IS_SHELL=false;if(Module["ENVIRONMENT"]){if(Module["ENVIRONMENT"]==="WEB"){ENVIRONMENT_IS_WEB=true}else if(Module["ENVIRONMENT"]==="WORKER"){ENVIRONMENT_IS_WORKER=true}else if(Module["ENVIRONMENT"]==="NODE"){ENVIRONMENT_IS_NODE=true}else if(Module["ENVIRONMENT"]==="SHELL"){ENVIRONMENT_IS_SHELL=true}else{throw new Error("Module['ENVIRONMENT'] value is not valid. must be one of: WEB|WORKER|NODE|SHELL.")}}else{ENVIRONMENT_IS_WEB=typeof window==="object";ENVIRONMENT_IS_WORKER=typeof importScrip

Error: write EPIPE
    at WriteWrap.afterWrite (net.js:833:14)

[art-frela]

Hi,

Try to download and use VSCODE insider - it's fine works! ;-) I'll be waiting new release VSCode ))

[art-frela]

or simple delete and install ext again... working fine

[utkarsh4321]

I am also facing the same issue. I also uninstall live-sass extension and also uninstall vs code but after installing both it still giving same error.please tell how to solve the problem.

[calbo-nl]

same problem for me, not for all projects though. I think it has to do with a specific folder structure/depth.

` C:\Users\XXX.vscode\extensions\ritwickdey.live-sass-3.0.0\node_modules\sasslib\sass.sync.js:61 var Module=typeof Module!=="undefined"?Module:{};var moduleOverrides={};var key;for(key in Module){if(Module.hasOwnProperty(key)){moduleOverrides[key]=Module[key]}}Module["arguments"]=[];Module["thisProgram"]="./this.program";Module["quit"]=(function(status,toThrow){throw toThrow});Module["preRun"]=[];Module["postRun"]=[];var ENVIRONMENT_IS_WEB=false;var ENVIRONMENT_IS_WORKER=false;var ENVIRONMENT_IS_NODE=false;var ENVIRONMENT_IS_SHELL=false;if(Module["ENVIRONMENT"]){if(Module["ENVIRONMENT"]==="WEB"){ENVIRONMENT_IS_WEB=true}else if(Module["ENVIRONMENT"]==="WORKER"){ENVIRONMENT_IS_WORKER=true}else if(Module["ENVIRONMENT"]==="NODE"){ENVIRONMENT_IS_NODE=true}else if(Module["ENVIRONMENT"]==="SHELL"){ENVIRONMENT_IS_SHELL=true}else{throw new Error("Module['ENVIRONMENT'] value is not valid. must be one of: WEB|WORKER|NODE|SHELL.")}}else{ENVIRONMENT_IS_WEB=typeof window==="object";ENVIRONMENT_IS_WORKER=typeof importSc

TypeError: MsgBody.forEach is not a function at Function.Show (C:\Users\XXX.vscode\extensions\ritwickdey.live-sass-3.0.0\out\src\OuputWindow.js:16:21) at Glob.getSassFiles.glob (C:\Users\XXX.vscode\extensions\ritwickdey.live-sass-3.0.0\out\src\appModel.js:127:48) at Glob.f (C:\Users\XXX.vscode\extensions\ritwickdey.live-sass-3.0.0\node_modules\once\once.js:25:25) at Glob.emit (events.js:182:13) at Glob._readdirError (C:\Users\XXX.vscode\extensions\ritwickdey.live-sass-3.0.0\node_modules\glob\glob.js:610:14) at Glob._readdirEntries.i (C:\Users\XXX.vscode\extensions\ritwickdey.live-sass-3.0.0\node_modules\glob\glob.js:553:12) at FSReqWrap.oncomplete (fs.js:141:20) `

[jdneto]

I have noticed that the problem happens when trying to use import for local .scss files, in my case all of them were in the same folder; when I removed import the error stopped happening.

[jdneto]

It was apparently an incompatibility with the plugin Color Highlight, after disabling it the problem disappeared even when using import.

[MisfitDesignStudio]

It was apparently an incompatibility with the plugin Color Highlight, after disabling it the problem disappeared even when using import.

This solved the problem for me too! Thanks!

[mvaneijgen]

It also happens with Spell Right

[varune-xposures]

It was apparently an incompatibility with the plugin Color Highlight, after disabling it the problem disappeared even when using import.

After disabling Color Highlight extension crashes are gone. Thanks

[norixx]

I run into crashes so many times with different extensions. My problem is I don't want to disable other extensions to avoid crashes. Looking forward to radical improvement.

[adhikari-anish]

It was apparently an incompatibility with the plugin Color Highlight, after disabling it the problem disappeared even when using import.

Thank you :)

[scarpeace]

It was apparently an incompatibility with the plugin Color Highlight, after disabling it the problem disappeared even when using import.

This solved my problem! Thanks!

[michael-dragomir]

It was apparently an incompatibility with the plugin Color Highlight, after disabling it the problem disappeared even when using import.

This solved my problem! Thank you!

[haroldao]

thank you 😩😭☺

[Mofunkles]

Also had this issue, also was due to Color Highlight extension. Though for anyone wanting the best of both worlds, there is another addon: Colorize which does the same thing only doesn't cause Live Sass Compiler to crash the extension host!

Also to note that two options need enabling in Colorize to achieve the same behaviour from Color Highlight:

• Uncheck colorize.hide_current_line_decorations otherwise it disables the colors on the current line.
• Enter the setting.json for colorize.colorized_variables and add your CSS preprocessor else your variables won't be highlighted.

[KlajdiZmalaj]

if you have a comment import and the imported file doesnt exist, like this for example it will crash :

//@import filename or

/@import filename/

(i removed all commented imports and it worked)

[kinglycodes]

I don't have the color highlight extension and it doesn't work. Also I don't have a wrong import in my style (import) scss file.

Is there another workaround?

[GuilhermeFerreiraAmorim]

It was apparently an incompatibility with the plugin Color Highlight, after disabling it the problem disappeared even when using import.

thanks dude. solved for me!

[dorukozerr]

It was apparently an incompatibility with the plugin Color Highlight, after disabling it the problem disappeared even when using import.

Really Thank you solved my problem also. <33

[BattleKing28]

Also had this issue, also was due to Color Highlight extension. Though for anyone wanting the best of both worlds, there is another addon: Colorize which does the same thing only doesn't cause Live Sass Compiler to crash the extension host!

Also to note that two options need enabling in Colorize to achieve the same behaviour from Color Highlight:

* Uncheck colorize.hide_current_line_decorations otherwise it disables the colors on the current line.

* Enter the setting.json for colorize.colorized_variables and add your CSS preprocessor else your variables won't be highlighted.

thankyou so much man , you're a life saver....

[anshumanUTD21]

It was apparently an incompatibility with the plugin Color Highlight, after disabling it the problem disappeared even when using import.

thank you brother :D saved so much time.