You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have encountered a problem with libsass while trying to build a Ionic Framework Application on Alpine Linux (ionic-team/ionic-app-scripts#955). I could localize the problem in the recursive implementation of str-replace function (similar to #1823) or in general any other form of recursive function call that exceed certain recursion depth (~10 - 20 depending on the system and function).
input.scss
This scss code is just for demonstration of the problem:
I'm pretty sure this is due to too small stack size. This is a compile time or/and runtime option which is not under libsass control. So nothing we can do here. Please follow upstream tickets about alpine linux support.
The problem is, that libsass fails with segmentation fault (SIGSEGV) without any further information about the source of the problem (recursion depth, stack overflow or whatever). From my point of view, it should print an error message and terminate without segmentation fault.
Rebuilding libsass and node-sass bindings with -O0 doesn't help, it still triggers SIGSEGV.
I have encountered a problem with libsass while trying to build a Ionic Framework Application on Alpine Linux (ionic-team/ionic-app-scripts#955). I could localize the problem in the recursive implementation of str-replace function (similar to #1823) or in general any other form of recursive function call that exceed certain recursion depth (~10 - 20 depending on the system and function).
input.scss
This scss code is just for demonstration of the problem:
Actual results
Using node-sass with this source produces a Segmentation fault on Alpine Linux (Tested with node 6 and 7)
Expected result
Clean termination of sass processing with error message similar to other platforms / Linux distributions:
version info:
Alpine Linux: 3.5 and 3.6 with nodejs and nodejs-current packages (NodeJS 6 and NodeJS 7).
The text was updated successfully, but these errors were encountered: