-
Notifications
You must be signed in to change notification settings - Fork 158
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
Segment Fault in 2.0.1 - 2.1.0pre3 and ruby 2.6.2p47 #133
Comments
Seems to be related to sass/sassc-rails#58 (comment) Happens when it hits any asset pipeline helper, like image-url() |
Also note, this is using rails 4.2
|
@glebm this might be helpful ==13258== Invalid read of size 4 ==13258== at 0x17FF1630: sass_value_get_tag (in /usr/local/rvm/gems/ruby-2.6.3-railsexpress/gems/sassc-2.1.0.pre3-x86_64-linux/lib/sassc/libsass.so) ==13258== by 0x180A2481: Sass::Eval::operator()(Sass::Function_Call*) (in /usr/local/rvm/gems/ruby-2.6.3-railsexpress/gems/sassc-2.1.0.pre3-x86_64-linux/lib/sassc/libsass.so) ==13258== by 0x1804F57D: Sass::Eval::operator()(Sass::List*) (in /usr/local/rvm/gems/ruby-2.6.3-railsexpress/gems/sassc-2.1.0.pre3-x86_64-linux/lib/sassc/libsass.so) ==13258== by 0x18033962: Sass::Expand::operator()(Sass::Declaration*) (in /usr/local/rvm/gems/ruby-2.6.3-railsexpress/gems/sassc-2.1.0.pre3-x86_64-linux/lib/sassc/libsass.so) ==13258== by 0x18103B71: ??? (in /usr/local/rvm/gems/ruby-2.6.3-railsexpress/gems/sassc-2.1.0.pre3-x86_64-linux/lib/sassc/libsass.so) ==13258== by 0x1803341A: Sass::Expand::operator()(Sass::Block*) (in /usr/local/rvm/gems/ruby-2.6.3-railsexpress/gems/sassc-2.1.0.pre3-x86_64-linux/lib/sassc/libsass.so) ==13258== by 0x18035CBD: Sass::Expand::operator()(Sass::Ruleset*) (in /usr/local/rvm/gems/ruby-2.6.3-railsexpress/gems/sassc-2.1.0.pre3-x86_64-linux/lib/sassc/libsass.so) ==13258== by 0x18103B71: ??? (in /usr/local/rvm/gems/ruby-2.6.3-railsexpress/gems/sassc-2.1.0.pre3-x86_64-linux/lib/sassc/libsass.so) ==13258== by 0x1803341A: Sass::Expand::operator()(Sass::Block*) (in /usr/local/rvm/gems/ruby-2.6.3-railsexpress/gems/sassc-2.1.0.pre3-x86_64-linux/lib/sassc/libsass.so) ==13258== by 0x180C1EA3: Sass::Context::compile() (in /usr/local/rvm/gems/ruby-2.6.3-railsexpress/gems/sassc-2.1.0.pre3-x86_64-linux/lib/sassc/libsass.so) ==13258== by 0x180C32F6: Sass::Data_Context::parse() (in /usr/local/rvm/gems/ruby-2.6.3-railsexpress/gems/sassc-2.1.0.pre3-x86_64-linux/lib/sassc/libsass.so) ==13258== by 0x1804CE7D: sass_compiler_parse (in /usr/local/rvm/gems/ruby-2.6.3-railsexpress/gems/sassc-2.1.0.pre3-x86_64-linux/lib/sassc/libsass.so) ==13258== Address 0x0 is not stack'd, malloc'd or (recently) free'd full report https://gist.github.com/ahorek/88a5bfc31a42d3be1f36783ae18ac3f4 |
Hitting the same issue, only happening in development mode in a Ubuntu docker container with |
Here is the beginning of my stack trace:
|
Am also being affected by this issue.
See attached below for my full stack traces and crash reports: |
See rails/sprockets#581 (comment) for a workaround |
* During Heroku deploys we can build a new container successfully, but the release phase fails with a seg fault with similar output to sass/sassc-ruby#133 * After a lot of cross referencing between this app and a recent working example of Heroku containers (https://github.com/LBHackney-IT/report-a-defect) it worked until Standard.rb was added and bumped this gem. Setting it backwards until a new version can be made fixed the issue. * Tests run, including standard. And the page is styled correctly with it's assets precompiled. There doesn't _look_ to be a negative impact of removing reverting minor update.
This (or something closely adjacent) is still happening with sassc 2.2.1 and ruby 2.7.0: https://github.com/puppetlabs/iac/runs/516329222
|
Hitting the same backtrace on OpenBSD, sassc-2.2.1 |
I still hit this or something similar when trying to hunt a memory leak with mwrap |
Same issue here: sassc 2.3.0 + ruby 2.6.6 on Ubuntu 18.04. |
check out rails/sprockets#633 |
For us an update to sassc 2.4.0 which included an update of ffi from 1.11.1 to 1.13.1 fixed it. sassc 2.2.1 brought a LoadError fix and 2.3.0 made the arch native flag default to false. @rompic & @mechiland should you still encounter this issue you may try installing like this: |
This is only occurring in a staging/ubuntu environment. Locally, on a MacOS/development environment, this is working fine.
The text was updated successfully, but these errors were encountered: