Skip to content
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

after install of compass-importer and node-sass ng serve ends with segmentation fault #950

Closed
thinkrapido opened this issue May 28, 2016 · 5 comments
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent type: bug/fix

Comments

@thinkrapido
Copy link

Please provide us with the following information:

  1. OS
    ubuntu 16.04
  1. Versions.
    angular-cli: 1.0.0-beta.5
    node: 6.2.0
    os: linux x64
  2. Repro steps. Was this an app that wasn't created using the CLI? What change did you
    do on your code? etc.

npm install compass-importer node-sass

ng serve

OUTPUT:

(node:10586) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
Livereload server on http://localhost:49152
Serving on http://localhost:4200/
Segmentation fault (core dumped)
  1. The log given by the failure. Normally this include a stack trace and some
    more information.
    no stack trace
  2. Mention any other details that might be useful.

default css file renamed to scss

no other changes

@thinkrapido
Copy link
Author

thinkrapido commented May 28, 2016

I debugged it so far, that I can say it is not an angular-cli problem.

It has to do with the binding.node module of node-sass, where the render_sync function causes the problem.

See: sass/node-sass#1572

@thinkrapido
Copy link
Author

It is a problem with using both modules node-sass and compass-importer.

I deleted compass-importer so that only node-sass is present.
This config causes no segmentation fault.

Has someone an idea of this coincidence?

See: sass/node-sass#1572

@thinkrapido thinkrapido reopened this May 29, 2016
@filipesilva
Copy link
Contributor

This seems to be a bug with our compass support.

@filipesilva filipesilva added type: bug/fix command: build P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent labels Jun 1, 2016
@filipesilva
Copy link
Contributor

Closed as this issue was made obsolete by #1455.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent type: bug/fix
Projects
None yet
Development

No branches or pull requests

2 participants