sassc-rails icon indicating copy to clipboard operation
sassc-rails copied to clipboard

Seg fault during development

Open willhaslett opened this issue 6 years ago • 9 comments

Starting recently after some gem updates, seemingly randomly, saving a .scss file during development results in this segmentation fault:

/usr/local/bundle/gems/sassc-2.0.1/lib/sassc/engine.rb:42: [BUG] Segmentation fault at 0x0000000000000000
ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-linux]

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

willhaslett avatar Apr 13 '20 14:04 willhaslett

Also seeing this during a heroku build of an application:

 /tmp/build_5e0a535a3d8650948298370ae436c71c/vendor/bundle/ruby/2.7.0/gems/sassc-2.4.0/lib/sassc/engine.rb:43: [BUG] Segmentation fault at 0x0000000000000000
       ruby 2.7.1p83 (2020-03-31 revision a0c7c23c9c) [x86_64-linux]`

perkinss avatar Jun 09 '20 01:06 perkinss

Updating sass-rails (and using sassc-rails) has been doing this for many/all of my Rails applications

gordonbisnor avatar Jun 09 '20 14:06 gordonbisnor

Same problem here.

/home/me/.rvm/gems/ruby-2.6.5/gems/sassc-2.4.0/lib/sassc/engine.rb:43: [BUG] Segmentation fault at 0x0000000000000000 ruby 2.6.5p114 (2019-10-01 revision 67812) [x86_64-linux]

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! :)

richhollis avatar Jul 30 '20 12:07 richhollis

Also hitting this randomly during container builds. Anyone found a fix yet?

mcg avatar Oct 28 '20 13:10 mcg

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?

evereichmann avatar Nov 16 '20 23:11 evereichmann

I was using sematic styling and linking like @import "semantic-ui"; @import "semantic-ui/collections/menu"; and once I removed that I stopped getting that error

evereichmann avatar Nov 16 '20 23:11 evereichmann

same issue, anyone found a solution yet...?

diana-galvao avatar Jan 31 '21 02:01 diana-galvao

Has anyone figured this out? I came back to a project and every time I run rails s it crashes on the first render.

ChristianPavilonis avatar Dec 08 '21 16:12 ChristianPavilonis

FWIW, my seg faults with Sprockets 4 seem to be going away after disabling concurrent compilation (export_concurrent = false): https://github.com/rails/sprockets/issues/633#issuecomment-774762509

sbull avatar Dec 10 '21 22:12 sbull