-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
Version 10+ breaks with a sassc segmentation fault #191
Comments
Are you using sprockets 4.x ? BTW, I believe there's nothing in this gem that could cause sassc to break. |
Yes I'm using sprockets 4.x. I've also traced this problem to look similar to what other people experience with sprockets 4.x. Unfortunately I've tested if downgrading sprockets to 3.x helps but had to find out it doesn't. |
Tracked it further to an incompatability between rails_admin together with Version 10.x of this gem. |
rails_admin uses xxx.scss.erb files. Could be that this comes from sprockets 4.x are not automatically chainable? |
Can you reproduce this with a minimal rails app? I still doubt this has anything to do with the changes from 9.x to 10.x . |
After much experimenting I've found out that with the newest 10.x release this disappears. Still not yet sure what it was but for the moment it works 👍 |
When using Version 10+ I end up in a segmentation fault of sassc while pre-compiling.
When using Version 9.x all works nicely.
The segmentation fault is in the sassc gem /lib/sassc/engine.rb:43
Tried to figure out if the stems from the ruby code within autoprefixer-rails or the javascript and must assume it is an interaction between the two of them.
Not sure if this can and will be fixed within autoprefixer-rails but since sassc is officially deprecated this is where I'll start finding help. Thanks
The text was updated successfully, but these errors were encountered: