Exit status 3221225725 since node-sass > 4.1.1 #1863

mriehema · 2017-01-18T14:24:49Z

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/[email protected]
  `-- [email protected]
    `-- [email protected]

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/[email protected] 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

The text was updated successfully, but these errors were encountered:

nschonni · 2017-01-19T02:06:23Z

Can you reproduce this without running through grunt?

xzyfer · 2017-01-19T02:22:38Z

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

xzyfer · 2017-01-27T02:30:01Z

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

mriehema · 2017-03-15T16:10:51Z

FYI: just updated to grunt-sass 2.0.0 with a clean workspace. So I got [email protected]. 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! @[email protected] production: `grunt production`
npm ERR! Exit status 3221225725

mriehema · 2017-03-31T08:53:26Z

Any news on Exit status 3221225725?

mriehema · 2017-05-03T14:02:03Z

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 · 2017-05-03T14:47:19Z

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 · 2017-05-03T16:09:25Z

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 · 2017-05-03T16:50:12Z

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 · 2017-05-04T09:24:04Z

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

saper · 2017-05-07T09:44:37Z

When did we change versions of Visual Studio from 2013 to 2015?

Also do things change if you try different versions of node?

mriehema · 2017-05-08T15:12:43Z

I testet it with 7.10.0, 6.9.5, 6.10.3 and 4.8.3. Same result.

I played with my example code again and it looks like it depends on the length of the $svg. If I shorten the string or remove one of the calls str-replace in the loop, it works. str-replace uses str-slice, which was changed in libsass 3.4.1, see sass/libsass#2240

saper · 2017-05-08T21:34:30Z

Well, this might be #1289 str-replace is a stack-eating monster. Maybe running this in the debugger may reveal a huge stack that is full?

mriehema · 2017-05-09T13:53:39Z

Sorry, I'm not familiar with C++ Debugger. Could you tell me, what to do and I will give you all results you need.

saper · 2017-05-09T15:06:35Z

Do you have Visual Studio installed? Do you have ntsd, cdb and WinDbg debuggers installed? They can be installed independently of Visual Studio as a Debugging Tools for Windows (WinDbg, KD, CDB, NTSD)

xzyfer · 2018-03-10T10:31:38Z

This is probably fixed in 4.8.0

vedi · 2018-06-15T14:48:05Z

experiencing the same in 4.8.0 and 4.9.0

xzyfer · 2018-06-15T14:53:07Z

@vedi this comment is not useful without a reproducible test case

vedi · 2018-06-15T15:06:31Z

sorry, did not put it, because it looks similar with the initial one:

Win10 x64
[email protected]
[email protected]

If I have long inlined svg, node-sass just silently stops. If I use it through babel I get
Command failed with exit code 3221225725.

xzyfer · 2018-06-15T15:25:21Z

Please provide an actual code sample we can use to reproduce the issue ourselves.

…

On Fri., 15 Jun. 2018, 5:06 pm Fedor Shubin, ***@***.***> wrote: sorry, did not put it, because it looks similar with the initial one: Win10 x64 ***@***.*** ***@***.*** If I have long inlined svg node-sass just silently stops. If I use it through babel I get Command failed with exit code 3221225725. — 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/AAjZWBohrAli7FgUfZkVvg5Wi-wcvUzUks5t881_gaJpZM4Lm8MF> .

vedi · 2018-06-15T16:27:04Z

I put isolated reproducible case here:
https://gist.github.com/vedi/df8505935623a98b91ac26df742a750c

And downgrading to v4.1.1 did not help. I have the same issue here.

nschonni added Node 6 OS - Windows labels Jan 19, 2017

xzyfer closed this as completed Jan 19, 2017

xzyfer reopened this Jan 27, 2017

xzyfer added the External - LibSass label Jan 27, 2017

mriehema mentioned this issue May 4, 2017

Exit status 3221225477 trying to run lifecycle scripts on Windows npm/npm#11024

Closed

xzyfer mentioned this issue Mar 10, 2018

Release LibSass 3.5.0 support #2275

Closed

xzyfer closed this as completed Mar 10, 2018

jdalton mentioned this issue Mar 11, 2019

Exit status 3221225725 since [email protected] standard-things/esm#745

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Exit status 3221225725 since node-sass > 4.1.1 #1863

Exit status 3221225725 since node-sass > 4.1.1 #1863

mriehema commented Jan 18, 2017 •

edited

Loading

nschonni commented Jan 19, 2017

xzyfer commented Jan 19, 2017 •

edited

Loading

xzyfer commented Jan 27, 2017

mriehema commented Mar 15, 2017

mriehema commented Mar 31, 2017

mriehema commented May 3, 2017

xzyfer commented May 3, 2017

mriehema commented May 3, 2017

xzyfer commented May 3, 2017 via email

mriehema commented May 4, 2017 •

edited

Loading

saper commented May 7, 2017 •

edited

Loading

mriehema commented May 8, 2017

saper commented May 8, 2017

mriehema commented May 9, 2017

saper commented May 9, 2017

xzyfer commented Mar 10, 2018

vedi commented Jun 15, 2018 •

edited

Loading

xzyfer commented Jun 15, 2018

vedi commented Jun 15, 2018 •

edited

Loading

xzyfer commented Jun 15, 2018 via email

vedi commented Jun 15, 2018 •

edited

Loading

Exit status 3221225725 since node-sass > 4.1.1 #1863

Exit status 3221225725 since node-sass > 4.1.1 #1863

Comments

mriehema commented Jan 18, 2017 • edited Loading

nschonni commented Jan 19, 2017

xzyfer commented Jan 19, 2017 • edited Loading

xzyfer commented Jan 27, 2017

mriehema commented Mar 15, 2017

mriehema commented Mar 31, 2017

mriehema commented May 3, 2017

xzyfer commented May 3, 2017

mriehema commented May 3, 2017

xzyfer commented May 3, 2017 via email

mriehema commented May 4, 2017 • edited Loading

saper commented May 7, 2017 • edited Loading

mriehema commented May 8, 2017

saper commented May 8, 2017

mriehema commented May 9, 2017

saper commented May 9, 2017

xzyfer commented Mar 10, 2018

vedi commented Jun 15, 2018 • edited Loading

xzyfer commented Jun 15, 2018

vedi commented Jun 15, 2018 • edited Loading

xzyfer commented Jun 15, 2018 via email

vedi commented Jun 15, 2018 • edited Loading

mriehema commented Jan 18, 2017 •

edited

Loading

xzyfer commented Jan 19, 2017 •

edited

Loading

mriehema commented May 4, 2017 •

edited

Loading

saper commented May 7, 2017 •

edited

Loading

vedi commented Jun 15, 2018 •

edited

Loading

vedi commented Jun 15, 2018 •

edited

Loading

vedi commented Jun 15, 2018 •

edited

Loading