segfault on 2.3.0 #197
Comments
|
Same here at sassc-2.3.0/lib/sassc/engine.rb:43: [BUG] Segmentation fault at 0x0000000000000000 |
|
I also encounter it sometimes on Not including runtime |
|
Same here, it does not always fail but it fails a lot. I use the Ruby docker image 2.7 in GitlabCI. |
|
I reverted back to the previous version but here I have the same issue. It does seems to be related to the @jcoyne did you find a workaround for this? |
|
@johan-smits I stopped using sassc and switched to the npm version 😆 |
|
I have found a rails workaround for this: |
|
@tilhoft this worked for me to. |
|
@tilhoft I am brand new to Rails, can you pls specify in which file I should write this code? |
|
@akshathkaushal I wrote it to config/application.rb |
Added this to the end of application.rb Unfortunately, still segfaults :-( |
For me as well. Still segfaults. |
salimhb
added a commit
to railslove/rcvr-api
that referenced
this issue
Jun 4, 2020
salimhb
added a commit
to railslove/rcvr-api
that referenced
this issue
Jun 4, 2020
|
I'm seeing a segfault in my test environment (Ubuntu 16.04 container in aws codebuild) but not locally (Ubuntu 18.04), both are ruby 2.6.1. Latest, not working: I reverted each of the above gems one by one to the following previously known good versions (for me) and it is now working again. I haven't tried a mix and match or only changing a single gem to see exactly which one it is. I identified these gems just by what was blowing up in the control frame dump. Working: Control Frame Dump Example: |
|
I have a core file, if someone is interested. It will only stay up for the next few days though. https://send.firefox.com/download/5a2c462c6be5cc01/#ENKEY7c1f7RdQp5vuRTATQ |
|
This was happening to me on ruby 2.5.8p224 in and the fix disabling Running in a docker container (can be found on the project). |
|
I was about to update my Rails (6.0.3.3) project from Ruby 2.7.1 to 2.7.2, at Ruby 2.7.1 the above mentioned rails workaround fixed, and on production server (Ubuntu 18.04.5 LTS) still working, but on macOS development environment there is a new segfault...weird..and very annoying |
I have the same kind of crash but only in production. Ruby 2.7.1 |
|
Add this before the rest of the code in config/initializers/assets.rb it worked for me as tilhoft suggested |
|
Maybe this was already mentioned somewhere, but I was able to consistently reproduce in ruby 2.7.2p137, but it doesn't appear to occur in ruby 2.7.1p83 |
nicholasnadel
referenced
this issue
in chapmanu/cascade-assets
Apr 6, 2021
|
I have this issue and it kept get annoying. |
This was referenced Oct 4, 2021
|
This issue is still happening. |
|
@Kulgar I'm not in a position of authority with regard to this gem, but the C library that this gem wraps is deprecated, (see https://sass-lang.com/blog/libsass-is-deprecated). I've had better luck using sass via NPM or dart-sass. |
|
@jcoyne yeah, I switched to the new https://github.com/rails/cssbundling-rails which will be the default tech used in rails 7. |
4 tasks
This was referenced Feb 22, 2022
|
Any update on this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: