-
Notifications
You must be signed in to change notification settings - Fork 460
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
node-sass crashes when a parent selector is referenced but not included #1569
Comments
@xzyfer would love if this could make it in the 3.3 release |
The following is a more complex example with a mixin
Output on 3.3.3:
On 3.4.0
|
Here's what I got with the brand new libsass:
|
This one causes a segmentation violation on libsass 3.3.0.beta sass/libsass#1569
Crash backtrace for the complex case:
|
Thanks for checking up on this and adding the test cases. I'm AWAL next week for two weeks. If you need someone to test this on our .scss files, @HeadOnAPlate might be able to run those while I'm gone. |
This PR activates specs for sass/libsass#1569
When testing the latest node-sass@3.4.0-beta1 on our code base, node-sass plain crashes.
I traced it to the following (invalid code):
This seems to happen when a parent selector is referenced (the ampersand behind the .nihilo), but the parent node does not exist. node-sass/libsass should at least throw some kind of error. Now the process just seems to crash.
Following is the output on my system:
c:\Code\site2014\static\gulpfile.js build:scss --source file.scss
[15:49:13] Using gulpfile gulpfile.js
[15:49:13] Starting 'scss:options'...
[15:49:13] Using version: node-sass 3.4.0-beta1 (Wrapper) [JavaScript]
libsass 3.3.0-beta2 (Sass Compiler) [C/C++]
[15:49:13] Finished 'scss:options' after 1.19 ms
[15:49:13] Starting 'scss:compile'...
[15:49:13] [scss] : sync / expanded mode.
[15:49:13] [scss:compile] [1] [c:\file.scss]
Process finished with exit code -1073741819 (0xC0000005)
The text was updated successfully, but these errors were encountered: