Segmentation fault with no error message

[tskarhed]

I tried to serve my application, but it wouldn't start. After a bit of work we figured out it was a stylesheet. After a bit more work we realized it was regular mistake:

.rating
    display: flex
        width: 100px
            .material-icons
                max-width: 20px

The obvious mistake is the .material-icons is displaced. I did not get an error message saying that, only (on OSx) segmentation fault.

I am running Windows 10.

Screenshot Windows

Screenshot OSx

[simonexmachina]

This is a node-sass issue. This module is a thin wrapper around node-sass. You're welcome to post this issue on the node-sass issue tracker.

[mike-north]

While it's true that the issue doesn't lie within this library, we still should assume responsibility for creating a good experience for consumers whenever possible. The issue here has to do with the version of libsass that node-sass v3.5.x pulls in. I've opened up an issue in broccoli-sass-source-maps with a proposed solution. Hope we can get a fix for this soon, as I have had to help dozens of people get past this while teaching workshops.

[simonexmachina]

There's a workaround here. I should add this to the README but I'm not at the computer.

[simonexmachina]

I've added docs for the workaround to ember-cli-sass.

[dustinfarris]

This appears to have been fixed in libsass 3.3.6. Recent versions of node-sass are using this latest libsass, so we should be able to simply upgrade the node-sass version and this issue will go away.

[dustinfarris]

Created upstream PR adopted-ember-addons/broccoli-sass-source-maps#20

[mike-north]

Would love to see a fix here. Part of the problem is that ember-cli 2.5 doesn't treat ember-cli-build.js properly in blueprints, so there's no way to set a working version of node-sass up for users automatically.

[simonexmachina]

Published v5.4.0 which upgrades node-sass

[ghost]

Hi,

I have the same problem, what is the explicit solution?....I'm use ember cli.....

This my devdependencies:

"devDependencies": {
"broccoli-asset-rev": "^2.4.2",
"ember-ajax": "^2.0.1",
"ember-cli": "2.7.0",
"ember-cli-app-version": "^1.0.0",
"ember-cli-babel": "^5.1.6",
"ember-cli-dependency-checker": "^1.2.0",
"ember-cli-htmlbars": "^1.0.3",
"ember-cli-htmlbars-inline-precompile": "^0.3.1",
"ember-cli-inject-live-reload": "^1.4.0",
"ember-cli-jshint": "^1.0.0",
"ember-cli-materialize": "0.22.0-beta.0",
"ember-cli-qunit": "^2.0.0",
"ember-cli-release": "^0.2.9",
"ember-cli-sass": "^5.5.1",
"ember-cli-sri": "^2.1.0",
"ember-cli-test-loader": "^1.1.0",
"ember-cli-uglify": "^1.2.0",
"ember-composability": "0.3.7",
"ember-data": "^2.7.0",
"ember-export-application-global": "^1.0.5",
"ember-keyboard": "1.0.3",
"ember-load-initializers": "^0.5.1",
"ember-material-design-icons-shim": "0.1.9",
"ember-materialize-shim": "0.2.3",
"ember-modal-dialog": "0.8.8",
"ember-new-computed": "1.0.3",
"ember-radio-button": "1.0.7",
"ember-resolver": "^2.0.3",
"ember-truth-helpers": "1.2.0",
"ember-welcome-page": "^1.0.1",
"loader.js": "^4.0.1",
"node-sass": "3.4.2"
},

Thanks!

[dustinfarris]

@jaider2523 you can get rid of the explicit node-sass dependency now.

[ghost]

@dustinfarris Oh Man.... Thanks......work fine....