-
Notifications
You must be signed in to change notification settings - Fork 104
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
Seg fault during development #143
Comments
Also seeing this during a heroku build of an application:
|
Updating sass-rails (and using sassc-rails) has been doing this for many/all of my Rails applications |
Same problem here.
I'm working on integrating a design at the moment and so changing styles quite a bit and it is happening almost every time I make a change. No problem with older Rails 5 projects only with a newer Rails 6 (with webpacker) problem. I tried downgrading sprockets to 3.7.2 as that seemed to work for some people but it hasn't worked for me. Any idea how we can get this fixed? It's manageable when only making the odd change but when actively working with styles it is a headache! :) |
Also hitting this randomly during container builds. Anyone found a fix yet? |
Getting this with a heroku build. I was able to deploy this app initially but now I'm getting Precompiling assets failed. Any direction on this issue? |
I was using sematic styling and linking like |
same issue, anyone found a solution yet...? |
Has anyone figured this out? I came back to a project and every time I run |
FWIW, my seg faults with Sprockets 4 seem to be going away after disabling concurrent compilation (export_concurrent = false): |
Starting recently after some gem updates, seemingly randomly, saving a .scss file during development results in this segmentation fault:
I can't provide specific steps to reproduce because this is happening unpredictably, in any of the app's stylesheets.
This is a production Rails 6 app that has been stable for years (originally Rails 5). The app is Dockerized, and the development setup has not changed in some time. What other information can I provide to help diagnose this? I'm hopeful that this error will not appear in production (precompiled), but the severity of the error is disconcerting.
Gemfile.lock.txt
The text was updated successfully, but these errors were encountered: