Exit status 3221225725 since node-sass > 4.1.1

[mriehema]

We're using node-sass via grunt-sass. Since node-sass got updated to 4.3 it fails on Windows (no problems with OSX and linux). With 4.1.1 we didn't have these problems.

• NPM version (npm -v):
  3.10.8
• Node version (node -v):
  6.9.1
• Node Process (node -p process.versions):

{ http_parser: '2.7.0',
  node: '6.9.1',
  v8: '5.1.281.84',
  uv: '1.9.1',
  zlib: '1.2.8',
  ares: '1.10.1-DEV',
  icu: '57.1',
  modules: '48',
  openssl: '1.0.2j' }

• Node Platform (node -p process.platform):
  win32
• Node architecture (node -p process.arch):
  x64
• node-sass version (node -p "require('node-sass').info"):

node-sass       4.3.0   (Wrapper)       [JavaScript]
libsass         3.4.3   (Sass Compiler) [C/C++]

• npm node-sass versions (npm ls node-sass):

`-- @coremedia/grunt-utils@1.0.0
  `-- grunt-sass@2.0.0
    `-- node-sass@4.3.0

Error message running sass via grunt via npm script:

...
Running "sass:build" (sass) task

npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "production"
npm ERR! node v6.9.1
npm ERR! npm  v3.10.8
npm ERR! code ELIFECYCLE
npm ERR! @coremedia/perfectchef-theme@1.0.0 production: `grunt production`
npm ERR! Exit status 3221225725
...

Running grunt sass exits without any exit code or error message.

Our workaround is to go back to grunt-sass 1.2.1 with node-sass 3.13.1

[nschonni]

Can you reproduce this without running through grunt?

[xzyfer]

Duplicate #1861. We're experiencing issues with grunt-sass atm.

[xzyfer]

This could also be a duplicate of #1854. Needs to confirm once 4.4.0 is stable.

[mriehema]

FYI: just updated to grunt-sass 2.0.0 with a clean workspace. So I got node-sass@4.5.0. but still the same exit code. :(

Running "sass:build" (sass) task

npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "production"
npm ERR! node v6.10.0
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! @foo-theme@1.0.0 production: `grunt production`
npm ERR! Exit status 3221225725

[mriehema]

Any news on Exit status 3221225725?

[mriehema]

Still broken, so I checked my sass files and found the some code causing this issue.

It's working in Codepen, see https://codepen.io/anon/pen/YVxwdG
But not with node-sass. Running the example scss from codepen with node-sass test.scss will exit without any output. :(

[xzyfer]

Noone has been able to reproduce Exit status 3221225725. As for your codepen I see the same output as Ruby Sass when testing with https://www.sassmeister.com/

[mriehema]

Can you run the code (which work in codepen and sassmeister) with node-sass as I described? I can't. Runnning node-sass directly will exit without any information. Running node-sass via npm script will cause this exit code.

See my example project: https://github.com/mriehema/node-sass-issue

[xzyfer]

Sessmeister is running node-sass when you select LibSass from the drop down. I also confirmed it running LibSass directly. Are you using the latest node-sass?

…

On 3 May 2017 6:09 pm, "Michael Riehemann" ***@***.***> wrote: Can you run the code (which work in codepen and sassmeister) with node-sass as I described? I can't. Runnning node-sass directly will exit without any information. Running node-sass via npm script will cause this exit code. See my example project: https://github.com/mriehema/node-sass-issue — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#1863 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAjZWCETmpu15tqzLmkLb_XT_rEMY30Eks5r2Ka1gaJpZM4Lm8MF> .

[mriehema]

Hi @xzyfer, I'm sorry to bother you, but did you check my example project? Please try to reproduce it.
I asked my colleagues to test it and all Windows user got the same error code (it doesn't matter, which node version they used.) but it works with macOS. This error occurs since 4.2.0. v4.1.1 was fine. I added a branch for that too: https://github.com/mriehema/node-sass-issue/tree/old-node-sass-version

EDIT: Some more informations:
It looks like only win32-x64 is affected. I run it in appveyor, which uses win32-ia32 and it works. And even on Ubuntu Shell on Windows with linux-x64 works.

Conclusion: LibSass has been bumped from 3.4.0 to 3.4.3 in v4.2.0. Something between these versions is causing this exit status for Windows x64. Should I open an issue in libsass for that?

Info:
Exit status 3221225725 = error code 0xc00000fd = stack overflow,
See https://support.microsoft.com/en-us/help/315937/how-to-trap-stack-overflow-in-a-visual-c-application